{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4488 exists.","fix":"No fix has been published for CVE-2009-4488 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-4488 is a critical vulnerability in n/a, published on 13 Jan 2010. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-4488 and fix it if it is affected.\n\nWhat it is: CVE-2009-4488 is a critical vulnerability in n/a, published on 13 Jan 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4488 exists.\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-2009-4488/ (Markdown: https://insights.sbomify.com/CVE-2009-4488/index.md)","id":"CVE-2009-4488","markdown":"https://insights.sbomify.com/CVE-2009-4488/index.md","name":"CVE-2009-4488","record":{"aliases":["DEBIAN-CVE-2009-4488","GHSA-xm68-4v8h-h9rf","UBUNTU-CVE-2009-4488"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Varnish cache server","requires_auth":"none","summary":"Varnish logs unsanitized HTTP requests, potentially allowing terminal escape sequence injection that could lead to command execution or file modification.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"varnish","vendor":"varnish.projects.linpro"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"Varnish 2.0.6 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.  NOTE: the vendor disputes the significance of this report, stating that \"This is not a security problem in Varnish or any other piece of software which writes a logfile. The real problem is the mistaken belief that you can cat(1) a random logfile to your terminal safely.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2010-01-11","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2010-01-11","kind":"exploitdb","ref":"33498","stars":null,"title":"Varnish 2.0.6 - 'Terminal Escape Sequence in Logs' Command Injection"}],"tier":"weaponised"},"has_fix":false,"headline":"Other in n/a","id":"CVE-2009-4488","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2009"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2009-4489"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2009-4487"},"products":["n/a"],"published":"2010-01-13","related":[{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2009-2936","kev_date_added":null,"published":"2010-04-05"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-21","vendors":["n/a"]},"summary":"Varnish logs unsanitized HTTP requests, potentially allowing terminal escape sequence injection that could lead to command execution or file modification.","url":"https://insights.sbomify.com/CVE-2009-4488/"}