{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-57040 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-57040 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-57040 is a critical vulnerability in n/a, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-57040 and fix it if it is affected.\n\nWhat it is: CVE-2024-57040 is a critical vulnerability in n/a, published on 26 Feb 2025. 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-2024-57040 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-2024-57040/ (Markdown: https://insights.sbomify.com/CVE-2024-57040/index.md)","id":"CVE-2024-57040","markdown":"https://insights.sbomify.com/CVE-2024-57040/index.md","name":"CVE-2024-57040","record":{"aliases":["GHSA-mjhr-3845-j2r5"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link router","requires_auth":"none","summary":"Attackers can gain root access to TP-Link routers by using hardcoded credentials found in firmware or via brute force.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tl-wr845n_firmware","vendor":"tp-link"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"TP-Link TL-WR845N devices with firmware TL-WR845N(UN)_V4_200909 and TL-WR845N(UN)_V4_190219 was discovered to contain a hardcoded password for the root account which can be obtained by analyzing downloaded firmware or via a brute force attack through physical access to the router. NOTE: The supplier has stated that this issue was fixed in firmware versions 250401 or later.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-03-18","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-03-18T02:49:42Z","kind":"github_poc","ref":"https://github.com/absholi7ly/Poc-CVE-2024-57040","stars":2,"title":"CVE-2024-57040 is a security vulnerability found in certain TP-Link TL-WR845N router models. Specifically, it involves a \"hardcoded\" password for the router's root account. This means a default, unchanging password is built into the router's software."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-57040","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"NodeBB Cross-site scripting (XSS) vulnerability","id":"CVE-2024-57041"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2024-57036"},"products":["n/a"],"published":"2025-02-26","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2024-46340","kev_date_added":null,"published":"2024-12-10"},{"cvss_score":8,"headline":"Information disclosure in n/a","id":"CVE-2024-46341","kev_date_added":null,"published":"2024-12-10"},{"cvss_score":8,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-50699","kev_date_added":null,"published":"2024-12-10"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["n/a"]},"summary":"Attackers can gain root access to TP-Link routers by using hardcoded credentials found in firmware or via brute force.","url":"https://insights.sbomify.com/CVE-2024-57040/"}