{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-1828 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-1828 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-1828 is a high-severity vulnerability in n/a, published on 2 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-2005-1828 and fix it if it is affected.\n\nWhat it is: CVE-2005-1828 is a high-severity vulnerability in n/a, published on 2 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-2005-1828 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-2005-1828/ (Markdown: https://insights.sbomify.com/CVE-2005-1828/index.md)","id":"CVE-2005-1828","markdown":"https://insights.sbomify.com/CVE-2005-1828/index.md","name":"CVE-2005-1828","record":{"aliases":["GHSA-x7hf-rfv2-7qqq"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"D-Link DSL router","requires_auth":"none","summary":"Remote attackers can obtain sensitive credentials stored in cleartext within the router configuration file.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dsl-504t_firmware","vendor":"dlink"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"D-Link DSL-504T stores usernames and passwords in cleartext in the router configuration file, which allows remote attackers to obtain sensitive information.","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-2005-1828","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2005-1829"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2005-1827"},"products":["n/a"],"published":"2005-06-02","related":[{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2005-1827","kev_date_added":null,"published":"2005-06-02"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive credentials stored in cleartext within the router configuration file.","url":"https://insights.sbomify.com/CVE-2005-1828/"}