{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-0919 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-0919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-0919 is a high-severity vulnerability in n/a, published on 16 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-0919 and fix it if it is affected.\n\nWhat it is: CVE-2009-0919 is a high-severity vulnerability in n/a, published on 16 Mar 2009. 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-2009-0919 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-2009-0919/ (Markdown: https://insights.sbomify.com/CVE-2009-0919/index.md)","id":"CVE-2009-0919","markdown":"https://insights.sbomify.com/CVE-2009-0919/index.md","name":"CVE-2009-0919","record":{"aliases":["GHSA-59v4-7p7v-xmg9"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"XAMPP web stack","requires_auth":"none","summary":"Remote attackers can gain unauthorized access to XAMPP components due to insecure default passwords for ProFTPD, MySQL, and phpMyAdmin.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"xampp","vendor":"apachefriends"}],"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":[{"id":"CWE-255","name":null}],"description":"XAMPP installs multiple packages with insecure default passwords, which makes it easier for remote attackers to obtain access via (1) the \"lampp\" default password for the \"nobody\" account within the included ProFTPD installation, (2) a blank default password for the \"root\" account within the included MySQL installation, (3) a blank default password for the \"pma\" account within the phpMyAdmin installation, and possibly other unspecified passwords.  NOTE: this was originally reported as a problem in DFLabs PTK, but this issue affects any product that is installed within the XAMPP environment, and should not be viewed as a vulnerability within that product. NOTE: DFLabs states that PTK is intended for use in a laboratory with \"no contact from / to internet.\"","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":"Hardcoded credentials in n/a","id":"CVE-2009-0919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2009"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2009-0920"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2009-0918"},"products":["n/a"],"published":"2009-03-16","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-8923","kev_date_added":null,"published":"2019-05-14"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-29376","kev_date_added":null,"published":"2022-05-23"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-11107","kev_date_added":null,"published":"2020-04-02"},{"cvss_score":7.3,"headline":"Buffer Overflow Vulnerability in XAMPP","id":"CVE-2024-0338","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2008-6498","kev_date_added":null,"published":"2009-03-20"},{"cvss_score":6.7,"headline":"Privilege escalation in n/a","id":"CVE-2022-47637","kev_date_added":null,"published":"2023-09-12"}],"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 gain unauthorized access to XAMPP components due to insecure default passwords for ProFTPD, MySQL, and phpMyAdmin.","url":"https://insights.sbomify.com/CVE-2009-0919/"}