{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2003-1039 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2003-1039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2003-1039 is a high-severity memory corruption vulnerability in n/a, published on 16 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2003-1039 and fix it if it is affected.\n\nWhat it is: CVE-2003-1039 is a high-severity memory corruption vulnerability in n/a, published on 16 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2003-1039 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-2003-1039/ (Markdown: https://insights.sbomify.com/CVE-2003-1039/index.md)","id":"CVE-2003-1039","markdown":"https://insights.sbomify.com/CVE-2003-1039/index.md","name":"CVE-2003-1039","record":{"aliases":["GHSA-pgw2-4cf2-2hqc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP mySAP.com","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on SAP mySAP.com components via buffer overflows in HTTP Host headers.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mysap_business_suite","vendor":"sap"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Multiple buffer overflows in the mySAP.com architecture for SAP allow remote attackers to execute arbitrary code via a long HTTP Host header to (1) Message Server, (2) Web Dispatcher, or (3) Application Server.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2003-1039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2003"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2003-1040"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2003-1038"},"products":["n/a"],"published":"2004-03-16","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code on SAP mySAP.com components via buffer overflows in HTTP Host headers.","url":"https://insights.sbomify.com/CVE-2003-1039/"}