# CVE-2014-9483: Security feature bypass in n/a

> Remote attackers can bypass security restrictions in Emacs, potentially exposing sensitive information or violating sandbox constraints.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hh37-cm5v-2qrh

## What is CVE-2014-9483?

CVE-2014-9483 is a high-severity vulnerability in n/a, published on 28 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Emacs 24.4 allows remote attackers to bypass security restrictions.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Gnu Emacs.

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

Upgrade to a fixed version.

## Is CVE-2014-9483 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6109](https://insights.sbomify.com/CVE-2007-6109/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-39331](https://insights.sbomify.com/CVE-2024-39331/): Code injection in n/a (critical 9.8)
- [CVE-2024-53920](https://insights.sbomify.com/CVE-2024-53920/): Code injection in n/a (high 7.8)
- [CVE-2024-30202](https://insights.sbomify.com/CVE-2024-30202/): Code injection in n/a (high 7.8)
- [CVE-2023-2491](https://insights.sbomify.com/CVE-2023-2491/): Command injection in emacs (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9483 is a high-severity vulnerability in n/a, published on 28 Aug 2017. 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-2014-9483 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-9483/ (Markdown: https://insights.sbomify.com/CVE-2014-9483/index.md)
```

## Sources

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

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