# CVE-2013-1124: Security feature bypass in n/a

> Cisco NAC Agent for Mac OS X fails to validate server certificates, allowing man-in-the-middle attackers to spoof Identity Services Engine servers.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-95pq-w267-m8p7

## What is CVE-2013-1124?

CVE-2013-1124 is a medium-severity vulnerability in n/a, published on 28 Feb 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Cisco Network Admission Control (NAC) agent on Mac OS X does not verify the X.509 certificate of an Identity Services Engine (ISE) server during an SSL session, which allows man-in-the-middle attackers to spoof ISE servers via an arbitrary certificate, aka Bug ID CSCub24309.

Weakness: CWE-310

## Which versions are affected by CVE-2013-1124?

It affects 1 product.


Products: Cisco Network Admission Control.

## How do I fix CVE-2013-1124?

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

## Is CVE-2013-1124 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1155](https://insights.sbomify.com/CVE-2008-1155/): Information disclosure in n/a (critical 10.0)
- [CVE-2006-4430](https://insights.sbomify.com/CVE-2006-4430/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1124 and fix it if it is affected.

What it is: CVE-2013-1124 is a medium-severity vulnerability in n/a, published on 28 Feb 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1124 in the wild and no public exploit code.

Affected product: n/a. 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-2013-1124/ (Markdown: https://insights.sbomify.com/CVE-2013-1124/index.md)
```

## Sources

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

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