{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1677 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1677 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1677 is a medium-severity vulnerability in n/a, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1677 and fix it if it is affected.\n\nWhat it is: CVE-2002-1677 is a medium-severity vulnerability in n/a, published on 21 Jun 2005. 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-2002-1677 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-2002-1677/ (Markdown: https://insights.sbomify.com/CVE-2002-1677/index.md)","id":"CVE-2002-1677","markdown":"https://insights.sbomify.com/CVE-2002-1677/index.md","name":"CVE-2002-1677","record":{"aliases":["GHSA-wfpg-gw9j-p5g3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MRTG configuration tool","requires_auth":"none","summary":"Remote attackers can determine the physical web root path via error messages from invalid parameters in 14all.cgi.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mrtgconfig","vendor":"mrtg"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"14all.cgi 1.1p15 in mrtgconfig allows remote attackers to determine the physical path to the web root directory via a request with an invalid cfg parameter, which generates an error message that reveals the path.","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":"Information disclosure in n/a","id":"CVE-2002-1677","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2002"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2002-1678"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2002-1676"},"products":["n/a"],"published":"2005-06-21","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 determine the physical web root path via error messages from invalid parameters in 14all.cgi.","url":"https://insights.sbomify.com/CVE-2002-1677/"}