# CVE-2014-1213: Missing authorization in n/a

> Local attackers can bypass anti-virus protection or cause denial of service by manipulating unprotected global and session objects in the Sophos Anti-Virus engine.

- **Severity:** Medium 5.6 (`AV:L/AC:L/Au:N/C:N/I:P/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:** 10 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r9jr-628j-pc37

## What is CVE-2014-1213?

CVE-2014-1213 is a medium-severity missing authorization vulnerability in n/a, published on 10 Feb 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sophos Anti-Virus engine (SAVi) before 3.50.1, as used in VDL 4.97G 9.7.x before 9.7.9, 10.0.x before 10.0.11, and 10.3.x before 10.3.1 does not set an ACL for certain global and session objects, which allows local users to bypass anti-virus protection, cause a denial of service (resource consumption, CPU consumption, and eventual crash) or spoof "ready for update" messages by performing certain operations on mutexes or events including (1) DataUpdateRequest, (2) MmfMutexSAV-****, (3) MmfMutexSAV-Info, (4) ReadyForUpdateSAV-****, (5) ReadyForUpdateSAV-Info, (6) SAV-****, (7) SAV-Info, (8) StateChange, (9) SuspendedSAV-****, (10) SuspendedSAV-Info, (11) UpdateComplete, (12) UpdateMutex, (13) UpdateRequest, or (14) SophosALMonSessionInstance, as demonstrated by triggering a ReadyForUpdateSAV event and modifying the UpdateComplete, UpdateMutex, and UpdateRequest objects.

Weakness: CWE-264

## Which versions are affected by CVE-2014-1213?

It affects 2 products.


Products: Sophos Scanning Engine, Sophos Sophos Anti-Virus.

## How do I fix CVE-2014-1213?

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

## Is CVE-2014-1213 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4787](https://insights.sbomify.com/CVE-2007-4787/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1213 and fix it if it is affected.

What it is: CVE-2014-1213 is a medium-severity missing authorization vulnerability in n/a, published on 10 Feb 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-1213 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-2014-1213/ (Markdown: https://insights.sbomify.com/CVE-2014-1213/index.md)
```

## Sources

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

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