{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2004-1391 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-1391 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-1391 is a medium-severity path traversal vulnerability in n/a, published on 6 Feb 2005. 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-2004-1391 and fix it if it is affected.\n\nWhat it is: CVE-2004-1391 is a medium-severity path traversal vulnerability in n/a, published on 6 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2004-1391 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-2004-1391/ (Markdown: https://insights.sbomify.com/CVE-2004-1391/index.md)","id":"CVE-2004-1391","markdown":"https://insights.sbomify.com/CVE-2004-1391/index.md","name":"CVE-2004-1391","record":{"aliases":["GHSA-9pxm-c827-5fjf"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"QNX RTP OS","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary code by manipulating the PATH variable in the PPPoE daemon, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rtos","vendor":"qnx"},{"product":"rtp","vendor":"qnx"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Untrusted execution path vulnerability in the PPPoE daemon (PPPoEd) in QNX RTP 6.1 allows local users to execute arbitrary programs by modifying the PATH environment variable to point to a malicious mount program.","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":"Path traversal in n/a","id":"CVE-2004-1391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2004"},"n_packages":0,"n_references":6,"next":{"headline":"Path traversal in n/a","id":"CVE-2004-1392"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2004-1390"},"products":["n/a"],"published":"2005-02-06","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-1390","kev_date_added":null,"published":"2005-02-06"},{"cvss_score":7.2,"headline":"Path traversal in n/a","id":"CVE-2005-1528","kev_date_added":null,"published":"2006-02-09"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2006-0621","kev_date_added":null,"published":"2006-02-09"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2006-0623","kev_date_added":null,"published":"2006-02-09"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2002-2040","kev_date_added":null,"published":"2005-07-14"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2002-2041","kev_date_added":null,"published":"2005-07-14"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2002-2042","kev_date_added":null,"published":"2005-07-14"}],"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":"Local attackers can execute arbitrary code by manipulating the PATH variable in the PPPoE daemon, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2004-1391/"}