# CVE-2022-48339: Command injection in n/a > Attackers can execute arbitrary code via shell metacharacters in file or directory names processed by the htmlfontify.el package in GNU Emacs. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 20 Feb 2023 - **Updated:** 18 Mar 2025 - **Also known as:** AZL-13682, DEBIAN-CVE-2022-48339, GHSA-jwxq-f9vm-725g, RHSA-2023:3481, UBUNTU-CVE-2022-48339, USN-5955-1 ## What is CVE-2022-48339? CVE-2022-48339 is a high-severity command injection vulnerability in n/a, published on 20 Feb 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description An issue was discovered in GNU Emacs through 28.2. htmlfontify.el has a command injection vulnerability. In the hfy-istext-command function, the parameter file and parameter srcdir come from external input, and parameters are not escaped. If a file name or directory name contains shell metacharacters, code may be executed. Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-1116 (Inaccurate Source Code Comments) ## Which versions are affected by CVE-2022-48339? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `emacs` | Red Hat:enterprise_linux:7::client | All versions | 1:24.3-23.el7_9.1 | | `emacs-common` | Red Hat:enterprise_linux:7::client | All versions | 1:24.3-23.el7_9.1 | | `emacs-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 1:24.3-23.el7_9.1 | | `emacs-el` | Red Hat:enterprise_linux:7::client | All versions | 1:24.3-23.el7_9.1 | | `emacs-filesystem` | Red Hat:enterprise_linux:7::client | All versions | 1:24.3-23.el7_9.1 | | `emacs-nox` | Red Hat:enterprise_linux:7::client | All versions | 1:24.3-23.el7_9.1 | | `emacs-terminal` | Red Hat:enterprise_linux:7::client | All versions | 1:24.3-23.el7_9.1 | | `emacs` | Red Hat:enterprise_linux:7::computenode | All versions | 1:24.3-23.el7_9.1 | | `emacs-common` | Red Hat:enterprise_linux:7::computenode | All versions | 1:24.3-23.el7_9.1 | | `emacs-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 1:24.3-23.el7_9.1 | | `emacs-el` | Red Hat:enterprise_linux:7::computenode | All versions | 1:24.3-23.el7_9.1 | | `emacs-nox` | Red Hat:enterprise_linux:7::computenode | All versions | 1:24.3-23.el7_9.1 | | `emacs-terminal` | Red Hat:enterprise_linux:7::computenode | All versions | 1:24.3-23.el7_9.1 | | `emacs` | Red Hat:enterprise_linux:7::server | All versions | 1:24.3-23.el7_9.1 | | `emacs-common` | Red Hat:enterprise_linux:7::server | All versions | 1:24.3-23.el7_9.1 | | `emacs-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 1:24.3-23.el7_9.1 | | `emacs-el` | Red Hat:enterprise_linux:7::server | All versions | 1:24.3-23.el7_9.1 | | `emacs-filesystem` | Red Hat:enterprise_linux:7::server | All versions | 1:24.3-23.el7_9.1 | | `emacs-nox` | Red Hat:enterprise_linux:7::server | All versions | 1:24.3-23.el7_9.1 | | `emacs-terminal` | Red Hat:enterprise_linux:7::server | All versions | 1:24.3-23.el7_9.1 | | `emacs` | Red Hat:enterprise_linux:7::workstation | All versions | 1:24.3-23.el7_9.1 | | `emacs-common` | Red Hat:enterprise_linux:7::workstation | All versions | 1:24.3-23.el7_9.1 | | `emacs-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 1:24.3-23.el7_9.1 | | `emacs-el` | Red Hat:enterprise_linux:7::workstation | All versions | 1:24.3-23.el7_9.1 | | `emacs-filesystem` | Red Hat:enterprise_linux:7::workstation | All versions | 1:24.3-23.el7_9.1 | | `emacs-nox` | Red Hat:enterprise_linux:7::workstation | All versions | 1:24.3-23.el7_9.1 | | `emacs-terminal` | Red Hat:enterprise_linux:7::workstation | All versions | 1:24.3-23.el7_9.1 | Products: Gnu Emacs. ## How do I fix CVE-2022-48339? Apply the vendor's patch. ## Is CVE-2022-48339 being exploited? There is no known exploitation of CVE-2022-48339 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-2022-48339 and fix it if it is affected. What it is: CVE-2022-48339 is a high-severity command injection vulnerability in n/a, published on 20 Feb 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-48339 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-2022-48339/ (Markdown: https://insights.sbomify.com/CVE-2022-48339/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48339 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48339 - OSV: https://osv.dev/vulnerability/CVE-2022-48339 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-48339/ Summaries are generated and may contain mistakes; the official description above is the record.