# CVE-2012-0334: Cisco IronPort Web Security Appliance AsyncOS software prior to 7.5 has a SSL Certificate Caching vulnerability which could allow man-in-the


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 15 Jan 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-vwvh-jw4m-wvv2

## What is CVE-2012-0334?

CVE-2012-0334 is a medium-severity vulnerability in Cisco IronPort Web Security Appliance AsyncOS, published on 15 Jan 2020. 

### Official description

Cisco IronPort Web Security Appliance AsyncOS software prior to 7.5 has a SSL Certificate Caching vulnerability which could allow man-in-the-middle attacks

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-0334?

It affects 1 product.


Products: Cisco Ironport Web Security Appliance.

## How do I fix CVE-2012-0334?

No fix has been published for CVE-2012-0334 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-0334 being exploited?

There is no known exploitation of CVE-2012-0334 in the wild and no public exploit code.

## Other vulnerabilities in Cisco IronPort Web Security Appliance AsyncOS

- [CVE-2012-1326](https://insights.sbomify.com/CVE-2012-1326/): Security feature bypass in IronPort Web Security Appliance (high 7.4)
- [CVE-2012-1316](https://insights.sbomify.com/CVE-2012-1316/): Security feature bypass in IronPort Web Security Appliance (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0334 and fix it if it is affected.

What it is: CVE-2012-0334 is a medium-severity vulnerability in Cisco IronPort Web Security Appliance AsyncOS, published on 15 Jan 2020. 
Exploitation: There is no known exploitation of CVE-2012-0334 in the wild and no public exploit code.

Affected product: Cisco IronPort Web Security Appliance AsyncOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-0334/ (Markdown: https://insights.sbomify.com/CVE-2012-0334/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-0334
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-0334
- OSV: https://osv.dev/vulnerability/CVE-2012-0334

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-0334/
Summaries are generated and may contain mistakes; the official description above is the record.