# CVE-2024-39331: Code injection in n/a > Attackers can execute arbitrary code via malicious Org Mode link abbreviations that invoke unsafe functions like shell-command-to-string. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Jun 2024 - **Updated:** 22 Aug 2024 - **Also known as:** ALSA-2024:6510, AZL-42868, AZL-42925, CLSA-2024-1728934930, CLSA-2025-1752088235, DEBIAN-CVE-2024-39331, DLA-3848-1, DLA-3849-1, DSA-5718-1, DSA-5719-1, GHSA-hp3p-7892-f222, MGASA-2024-0276, OESA-2024-1816, RHSA-2024:4971, RHSA-2024:6203, RHSA-2024:6510, SUSE-SU-2024:2293-1, SUSE-SU-2024:2567-1, UBUNTU-CVE-2024-39331, openSUSE-SU-2024:14117-1, openSUSE-SU-2026:10228-1, openSUSE-SU-2026:20928-1 ## What is CVE-2024-39331? CVE-2024-39331 is a critical code injection vulnerability in n/a, published on 23 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In Emacs before 29.4, org-link-expand-abbrev in lisp/ol.el expands a %(...) link abbrev even when it specifies an unsafe function, such as shell-command-to-string. This affects Org Mode before 9.7.5. Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2024-39331? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `emacs` | AlmaLinux:9 | All versions | 1:27.2-10.el9_4 | | `emacs-common` | AlmaLinux:9 | All versions | 1:27.2-10.el9_4 | | `emacs-filesystem` | AlmaLinux:9 | All versions | 1:27.2-10.el9_4 | | `emacs-lucid` | AlmaLinux:9 | All versions | 1:27.2-10.el9_4 | | `emacs-nox` | AlmaLinux:9 | All versions | 1:27.2-10.el9_4 | | `emacs` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-common` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-common-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-filesystem` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-lucid` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-lucid-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-nox` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs-nox-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:27.2-10.el9_4 | | `emacs` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-common` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-common-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-lucid` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-lucid-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-nox` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-nox-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-terminal` | Red Hat:rhel_aus:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs` | Red Hat:rhel_aus:8.6::baseos | All versions | 1:26.1-7.el8_6.5 | | `emacs-filesystem` | Red Hat:rhel_aus:8.6::baseos | All versions | 1:26.1-7.el8_6.5 | | `emacs` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-common` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-common-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-lucid` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-lucid-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-nox` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-nox-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs-terminal` | Red Hat:rhel_e4s:8.6::appstream | All versions | 1:26.1-7.el8_6.5 | | `emacs` | Red Hat:rhel_e4s:8.6::baseos | All versions | 1:26.1-7.el8_6.5 | | `emacs-filesystem` | Red Hat:rhel_e4s:8.6::baseos | All versions | 1:26.1-7.el8_6.5 | | `emacs` | Red Hat:rhel_eus:8.8::appstream | All versions | 1:26.1-10.el8_8.6 | Products: Gnu Emacs. ## How do I fix CVE-2024-39331? Upgrade to a fixed version. ## Is CVE-2024-39331 being exploited? There is no known exploitation of CVE-2024-39331 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-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) - [CVE-2023-27985](https://insights.sbomify.com/CVE-2023-27985/): emacsclient-mail.desktop in Emacs 28.1 through 28.2 is vulnerable to shell command injections through a crafted mailto: URI. (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-39331 and fix it if it is affected. What it is: CVE-2024-39331 is a critical code injection vulnerability in n/a, published on 23 Jun 2024. 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-2024-39331 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-2024-39331/ (Markdown: https://insights.sbomify.com/CVE-2024-39331/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39331 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39331 - OSV: https://osv.dev/vulnerability/CVE-2024-39331 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-39331/ Summaries are generated and may contain mistakes; the official description above is the record.