{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0034 exists.","fix":"No fix has been published for CVE-2003-0034 yet. Limit exposure of the affected software until one is available.","what":"CVE-2003-0034 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 2003. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2003-0034 and fix it if it is affected.\n\nWhat it is: CVE-2003-0034 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 2003. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0034 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-2003-0034/ (Markdown: https://insights.sbomify.com/CVE-2003-0034/index.md)","id":"CVE-2003-0034","markdown":"https://insights.sbomify.com/CVE-2003-0034/index.md","name":"CVE-2003-0034","record":{"aliases":["GHSA-v4p3-h258-jr4j"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux printer drivers","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary code via a buffer overflow in the mtink status monitor using a long HOME environment variable.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mtink","vendor":"jean-jacques_sarton"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Buffer overflow in the mtink status monitor, as included in the printer-drivers package in Mandrake Linux, allows local users to execute arbitrary code via a long HOME environment variable.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2003-01-21","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2003-01-21","kind":"exploitdb","ref":"22189","stars":null,"title":"MTink 0.9.x - Printer Status Monitor Environment Variable Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2003-0034","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2003"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2003-0035"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2003-0033"},"products":["n/a"],"published":"2003-01-22","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2005-4604","kev_date_added":null,"published":"2006-01-02"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code via a buffer overflow in the mtink status monitor using a long HOME environment variable.","url":"https://insights.sbomify.com/CVE-2003-0034/"}