{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6972 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6972 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6972 is a high-severity vulnerability in n/a, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-6972 and fix it if it is affected.\n\nWhat it is: CVE-2019-6972 is a high-severity vulnerability in n/a, published on 19 Jun 2019. 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-2019-6972 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-2019-6972/ (Markdown: https://insights.sbomify.com/CVE-2019-6972/index.md)","id":"CVE-2019-6972","markdown":"https://insights.sbomify.com/CVE-2019-6972/index.md","name":"CVE-2019-6972","record":{"aliases":["GHSA-pmm5-wjxf-w7h9"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link router","requires_auth":"none","summary":"Attackers can easily decode and crack router credentials due to weak encoding and MD5 hashing, leading to unauthorized access.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tl-wr1043nd_firmware","vendor":"tp-link"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"An issue was discovered on TP-Link TL-WR1043ND V2 devices. The credentials can be easily decoded and cracked by brute-force, WordList, or Rainbow Table attacks. Specifically, credentials in the \"Authorization\" cookie are encoded with URL encoding and base64, leading to easy decoding. Also, the username is cleartext, and the password is hashed with the MD5 algorithm (after decoding of the URL encoded string with base64).","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":"Weak cryptography in n/a","id":"CVE-2019-6972","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-6973"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2019-6971"},"products":["n/a"],"published":"2019-06-19","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-6971","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2013-2646","kev_date_added":null,"published":"2020-02-03"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2018-16119","kev_date_added":null,"published":"2019-06-20"}],"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-04","vendors":["n/a"]},"summary":"Attackers can easily decode and crack router credentials due to weak encoding and MD5 hashing, leading to unauthorized access.","url":"https://insights.sbomify.com/CVE-2019-6972/"}