{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-2076 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-2076 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2076 is a low-severity vulnerability in n/a, published on 29 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-2076 and fix it if it is affected.\n\nWhat it is: CVE-2005-2076 is a low-severity vulnerability in n/a, published on 29 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2005-2076 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-2076/ (Markdown: https://insights.sbomify.com/CVE-2005-2076/index.md)","id":"CVE-2005-2076","markdown":"https://insights.sbomify.com/CVE-2005-2076/index.md","name":"CVE-2005-2076","record":{"aliases":["GHSA-39mv-7vmg-f2x8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HP Version Control Repository Manager","requires_auth":"high_privilege","summary":"Attackers with physical access can view partial proxy passwords due to improper handling of the '@' character in HP VCRM.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"version_control_repository_manager","vendor":"hp"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"HP Version Control Repository Manager (VCRM) before 2.1.1.730 does not properly handle the \"@\" character in a proxy password, which could allow attackers with physical access to obtain portions of the password when it is displayed to the screen.","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-2076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-2077"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-2075"},"products":["n/a"],"published":"2005-06-29","related":[{"cvss_score":8.8,"headline":"File upload in Version Control Repository Manager (VCRM)","id":"CVE-2016-8515","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":8,"headline":"Cross-site request forgery in Version Control Repository Manager (VCRM)","id":"CVE-2016-8513","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2015-5409","kev_date_added":null,"published":"2015-08-26"},{"cvss_score":6.8,"headline":"Information disclosure in n/a","id":"CVE-2015-5411","kev_date_added":null,"published":"2015-08-26"},{"cvss_score":6.5,"headline":"A remote information disclosure in HPE Version Control Repository Manager (VCRM) was found.","id":"CVE-2016-8514","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":6.5,"headline":"Denial of service in Version Control Repository Manager (VCRM)","id":"CVE-2017-5787","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":6.5,"headline":"Code injection in n/a","id":"CVE-2015-5410","kev_date_added":null,"published":"2015-08-26"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers with physical access can view partial proxy passwords due to improper handling of the '@' character in HP VCRM.","url":"https://insights.sbomify.com/CVE-2005-2076/"}