# CVE-2007-2523: Privilege escalation in n/a

> Local attackers can exploit weak permissions and a buffer overflow in CA Anti-Virus to gain elevated privileges and execute arbitrary code.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j5vw-526q-m7h7

## What is CVE-2007-2523?

CVE-2007-2523 is a high-severity vulnerability in n/a, published on 11 May 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CA Anti-Virus for the Enterprise r8 and Threat Manager r8 before 20070510 use weak permissions (NULL security descriptor) for the Task Service shared file mapping, which allows local users to modify this mapping and gain privileges by triggering a stack-based buffer overflow in InoCore.dll before 8.0.448.0.

## Which versions are affected by CVE-2007-2523?

It affects 2 products.


Products: Broadcom Integrated Threat Management, Ca Anti-Virus for the Enterprise.

## How do I fix CVE-2007-2523?

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

## Is CVE-2007-2523 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2523 exists.

Public exploit code:

- CA (Multiple Products) - Console Server / 'InoCore.dll' Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2523 and fix it if it is affected.

What it is: CVE-2007-2523 is a high-severity vulnerability in n/a, published on 11 May 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2523 exists.

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-2007-2523/ (Markdown: https://insights.sbomify.com/CVE-2007-2523/index.md)
```

## Sources

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

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