{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-1999-1513 in the wild and no public exploit code.","fix":"No fix has been published for CVE-1999-1513 yet. Limit exposure of the affected software until one is available.","what":"CVE-1999-1513 is a high-severity vulnerability in n/a, published on 12 Sep 2001. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-1999-1513 and fix it if it is affected.\n\nWhat it is: CVE-1999-1513 is a high-severity vulnerability in n/a, published on 12 Sep 2001. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-1999-1513 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-1513/ (Markdown: https://insights.sbomify.com/CVE-1999-1513/index.md)","id":"CVE-1999-1513","markdown":"https://insights.sbomify.com/CVE-1999-1513/index.md","name":"CVE-1999-1513","record":{"aliases":["GHSA-gwm8-rgj9-362f"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"3Com network hub","requires_auth":"low_privilege","summary":"A read-only SNMP community string exposes the full table of community strings on 3Com SuperStack II hubs, allowing attackers to gain unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"superstack_ii_hub","vendor":"3com"}],"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":"Management information base (MIB) for a 3Com SuperStack II hub running software version 2.10 contains an object identifier (.1.3.6.1.4.1.43.10.4.2) that is accessible by a read-only community string, but lists the entire table of community strings, which could allow attackers to conduct unauthorized 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":"Information disclosure in n/a","id":"CVE-1999-1513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"1999"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-1999-1514"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-1999-1512"},"products":["n/a"],"published":"2001-09-12","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":"A read-only SNMP community string exposes the full table of community strings on 3Com SuperStack II hubs, allowing attackers to gain unauthorized access.","url":"https://insights.sbomify.com/CVE-1999-1513/"}