dbcve.org
Content Security Management ApplianceApplication · Cisco

CVE-2021-1129

MEDIUM · 5.3 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the authentication for the general purpose APIs implementation of Cisco Email Security Appliance (ESA), Cisco Content Security Management Appliance (SMA), and Cisco Web Security Appliance (WSA) could allow an unauthenticated, remote attacker to access general system information and certain configuration information from an affected device. The vulnerability exists because a secure authentication token is not required when authenticating to the general purpose API. An attacker could exploit this vulnerability by sending a crafted request for information to the general purpose API on an affected device. A successful exploit could allow the attacker to obtain system and configuration information from the affected device, resulting in an unauthorized information disclosure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cisco ESA, SMA, and WSA appliances contain an authentication bypass vulnerability in their general purpose API implementation. The API does not require a secure authentication token, allowing unauthenticated remote attackers to send crafted requests and obtain system and configuration information from affected devices.

MitigationApply Cisco security updates for CVE-2021-1129 or disable the general purpose API if not needed; verify API access requires proper authentication after remediation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Content Security Management ApplianceApplication
Affected:= 12.5.0
Email Security ApplianceApplication
Affected:= 13.0.0
Web Security ApplianceApplication
Affected:= 11.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your appliance type
    Log into the device web interface or run 'show version' on the CLI to determine if the device is an Email Security Appliance (ESA), Web Security Appliance (WSA), or Security Management Appliance (SMA)
    Affected if The device is an ESA, SMA, or WSA appliance
  2. Check the installed firmware version
    Run 'show version' on the appliance CLI or check the version displayed in the web interface header
    Affected if The version is exactly 12.5.0 for SMA, exactly 13.0.0 for ESA, or exactly 11.8.0 for WSA
  3. Confirm the general purpose API is enabled
    Check the appliance configuration for the 'general-purpose API' or 'API' settings in the web interface under the applicable management or system settings section, or review the CLI output for API-related configuration
    Affected if The general purpose API feature is enabled on the appliance
  4. Test API authentication requirement
    Send a crafted HTTP request to the API endpoint without including any authentication token or session cookie, using a tool like curl: curl -k -X GET https://<device-ip>/api/
    Affected if The API responds with system or configuration information without requiring any authentication credentials

You are affected if you run any of the exact listed versions (ESA 13.0.0, SMA 12.5.0, WSA 11.8.0) and the general purpose API is enabled, as the API will accept unauthenticated requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco security updates for CVE-2021-1129 or disable the general purpose API if not needed; verify API access requires proper authentication after remediation.

Fix this in Content Security Management Appliance Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1129 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data