{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2004-1976 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2004-1976 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-1976 is a high-severity vulnerability in n/a, published on 10 May 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-2004-1976 and fix it if it is affected.\n\nWhat it is: CVE-2004-1976 is a high-severity vulnerability in n/a, published on 10 May 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-2004-1976 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-1976/ (Markdown: https://insights.sbomify.com/CVE-2004-1976/index.md)","id":"CVE-2004-1976","markdown":"https://insights.sbomify.com/CVE-2004-1976/index.md","name":"CVE-2004-1976","record":{"aliases":["GHSA-7pjp-26r9-pjjc"],"analysis":{"component_type":"network_device","fix_type":"configuration_change","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Broadband router","requires_auth":"none","summary":"Remote attackers can gain unauthorized access to SMC Barricade routers because remote administration is enabled by default on port 1900.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smc7004vbr","vendor":"smc_networks"}],"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":"SMC Barricade broadband router 7008ABR and 7004VBR enable remote administration by default, which allows remote attackers to gain access by connecting to port 1900.","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-2004-1976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2004"},"n_packages":0,"n_references":5,"next":{"headline":"Denial of service in n/a","id":"CVE-2004-1977"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2004-1975"},"products":["n/a"],"published":"2005-05-10","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 gain unauthorized access to SMC Barricade routers because remote administration is enabled by default on port 1900.","url":"https://insights.sbomify.com/CVE-2004-1976/"}