{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-48338 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-48338 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."},"fix_prompt":"Check this codebase for CVE-2022-48338 and fix it if it is affected.\n\nWhat it is: CVE-2022-48338 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.\nExploitation: There is no known exploitation of CVE-2022-48338 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-48338/ (Markdown: https://insights.sbomify.com/CVE-2022-48338/index.md)","id":"CVE-2022-48338","markdown":"https://insights.sbomify.com/CVE-2022-48338/index.md","name":"CVE-2022-48338","record":{"aliases":["AZL-13681","DEBIAN-CVE-2022-48338","GHSA-hm6m-2xg8-mc5q","UBUNTU-CVE-2022-48338"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GNU Emacs","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands via malicious Ruby source files in GNU Emacs due to unescaped parameters in ruby-mode.el.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"emacs","vendor":"gnu"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"An issue was discovered in GNU Emacs through 28.2. In ruby-mode.el, the ruby-find-library-file function has a local command injection vulnerability. The ruby-find-library-file function is an interactive function, and bound to C-c C-f. Inside the function, the external command gem is called through shell-command-to-string, but the feature-name parameters are not escaped. Thus, malicious Ruby source files may cause commands to be executed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Command injection in n/a","id":"CVE-2022-48338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2022-48339"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-48337"},"products":["n/a"],"published":"2023-02-20","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-6109","kev_date_added":null,"published":"2007-12-07"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-39331","kev_date_added":null,"published":"2024-06-23"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2024-53920","kev_date_added":null,"published":"2024-11-27"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2024-30202","kev_date_added":null,"published":"2024-03-25"},{"cvss_score":7.8,"headline":"Command injection in emacs","id":"CVE-2023-2491","kev_date_added":null,"published":"2023-05-17"},{"cvss_score":7.8,"headline":"emacsclient-mail.desktop in Emacs 28.1 through 28.2 is vulnerable to shell command injections through a crafted mailto: URI.","id":"CVE-2023-27985","kev_date_added":null,"published":"2023-03-09"},{"cvss_score":7.8,"headline":"emacsclient-mail.desktop in Emacs 28.1 through 28.2 is vulnerable to Emacs Lisp code injections through a crafted mailto: URI with unescaped","id":"CVE-2023-27986","kev_date_added":null,"published":"2023-03-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via malicious Ruby source files in GNU Emacs due to unescaped parameters in ruby-mode.el.","url":"https://insights.sbomify.com/CVE-2022-48338/"}