{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-1999-1047 in the wild and no public exploit code.","fix":"No fix has been published for CVE-1999-1047 yet. Limit exposure of the affected software until one is available.","what":"CVE-1999-1047 is a high-severity vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-1999-1047 and fix it if it is affected.\n\nWhat it is: CVE-1999-1047 is a high-severity vulnerability in n/a, published on 9 Mar 2002. 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-1999-1047 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-1999-1047/ (Markdown: https://insights.sbomify.com/CVE-1999-1047/index.md)","id":"CVE-1999-1047","markdown":"https://insights.sbomify.com/CVE-1999-1047/index.md","name":"CVE-1999-1047","record":{"aliases":["GHSA-hf63-g73x-xwcf"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Gauntlet firewall","requires_auth":"none","summary":"Remote attackers can bypass firewall restrictions and avoid logging if BSDI patches are installed in a specific order.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gauntlet","vendor":"bsdi"}],"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":"When BSDI patches for Gauntlet 5.0 BSDI are installed in a particular order, Gauntlet allows remote attackers to bypass firewall access restrictions, and does not log the activities.","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":"Security feature bypass in n/a","id":"CVE-1999-1047","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"1999"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-1999-1048"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-1999-1046"},"products":["n/a"],"published":"2002-03-09","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-01","vendors":["n/a"]},"summary":"Remote attackers can bypass firewall restrictions and avoid logging if BSDI patches are installed in a specific order.","url":"https://insights.sbomify.com/CVE-1999-1047/"}