{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-1999-1422 in the wild and no public exploit code.","fix":"No fix has been published for CVE-1999-1422 yet. Limit exposure of the affected software until one is available.","what":"CVE-1999-1422 is a high-severity vulnerability in Slackware Slackware Linux, published on 12 Sep 2001. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-1999-1422 and fix it if it is affected.\n\nWhat it is: CVE-1999-1422 is a high-severity vulnerability in Slackware Slackware Linux, published on 12 Sep 2001. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-1999-1422 in the wild and no public exploit code.\n\nAffected product: Slackware Slackware Linux. 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-1999-1422/ (Markdown: https://insights.sbomify.com/CVE-1999-1422/index.md)","id":"CVE-1999-1422","markdown":"https://insights.sbomify.com/CVE-1999-1422/index.md","name":"CVE-1999-1422","record":{"aliases":["GHSA-rmw5-mwqc-865c"],"analysis":{"component_type":"operating_system","fix_type":"configuration_change","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Slackware Linux","requires_auth":"low_privilege","summary":"Local attackers can execute malicious code by exploiting the default PATH configuration containing the current directory.","user_interaction":"required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"slackware_linux","vendor":"slackware"}],"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":"The default configuration of Slackware 3.4, and possibly other versions, includes . (dot, the current directory) in the PATH environmental variable, which could allow local users to create Trojan horse programs that are inadvertently executed by other users.","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":"Misconfiguration in n/a","id":"CVE-1999-1422","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"slackware:slackware_linux","products":["slackware:slackware_linux"],"type":"misconfiguration","year":"1999"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-1999-1423"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-1999-1421"},"products":["n/a"],"published":"2001-09-12","related":[{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2013-7171","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2013-7172","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2003-0335","kev_date_added":null,"published":"2003-05-23"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-1999-0242","kev_date_added":null,"published":"2000-02-04"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-1999-0298","kev_date_added":null,"published":"2000-02-04"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-1999-1434","kev_date_added":null,"published":"2001-09-12"}],"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-01","vendors":["n/a"]},"summary":"Local attackers can execute malicious code by exploiting the default PATH configuration containing the current directory.","url":"https://insights.sbomify.com/CVE-1999-1422/"}