{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4769 exists.","fix":"No fix has been published for CVE-2009-4769 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-4769 is a critical vulnerability in n/a, published on 20 Apr 2010. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-4769 and fix it if it is affected.\n\nWhat it is: CVE-2009-4769 is a critical vulnerability in n/a, published on 20 Apr 2010. It can be exploited over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4769 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-4769/ (Markdown: https://insights.sbomify.com/CVE-2009-4769/index.md)","id":"CVE-2009-4769","markdown":"https://insights.sbomify.com/CVE-2009-4769/index.md","name":"CVE-2009-4769","record":{"aliases":["GHSA-72h8-x8gh-6pw7"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"httpdx web server","requires_auth":"unknown","summary":"Remote attackers can execute arbitrary code via format string vulnerabilities in httpdx's logging function, requiring logging to be enabled.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"httpdx","vendor":"jasper"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-134","name":"Use of Externally-Controlled Format String"}],"description":"Multiple format string vulnerabilities in the tolog function in httpdx 1.4, 1.4.5, 1.4.6, 1.4.6b, and 1.5 allow (1) remote attackers to execute arbitrary code via format string specifiers in a GET request to the HTTP server component when logging is enabled, and allow (2) remote authenticated users to execute arbitrary code via format string specifiers in a PWD command to the FTP server component.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2009-11-17","github_poc":0,"max_poc_stars":null,"metasploit":2,"nuclei":0,"refs":[{"date":"2009-11-17","kind":"metasploit","ref":"exploit/windows/ftp/httpdx_tolog_format","stars":null,"title":"HTTPDX tolog() Function Format String Vulnerability"},{"date":"2009-11-17","kind":"metasploit","ref":"exploit/windows/http/httpdx_tolog_format","stars":null,"title":"HTTPDX tolog() Function Format String Vulnerability"},{"date":"2010-08-25","kind":"exploitdb","ref":"16732","stars":null,"title":"httpdx - 'tolog()' Format String (Metasploit) (1)"},{"date":"2010-08-25","kind":"exploitdb","ref":"16794","stars":null,"title":"httpdx - 'tolog()' Format String (Metasploit) (2)"}],"tier":"weaponised"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2009-4769","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2009"},"n_packages":0,"n_references":5,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2009-4770"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2009-4768"},"products":["n/a"],"published":"2010-04-20","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-3711","kev_date_added":null,"published":"2009-10-16"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-3663","kev_date_added":null,"published":"2009-10-11"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2009-4770","kev_date_added":null,"published":"2010-04-20"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2009-4531","kev_date_added":null,"published":"2009-12-31"}],"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":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via format string vulnerabilities in httpdx's logging function, requiring logging to be enabled.","url":"https://insights.sbomify.com/CVE-2009-4769/"}