{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15498 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15498 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15498 is a medium-severity vulnerability in n/a, published on 26 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15498 and fix it if it is affected.\n\nWhat it is: CVE-2020-15498 is a medium-severity vulnerability in n/a, published on 26 Aug 2020. 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-2020-15498 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-2020-15498/ (Markdown: https://insights.sbomify.com/CVE-2020-15498/index.md)","id":"CVE-2020-15498","markdown":"https://insights.sbomify.com/CVE-2020-15498/index.md","name":"CVE-2020-15498","record":{"aliases":["GHSA-r3jr-p57g-fw5f"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ASUS router","requires_auth":"none","summary":"Attackers can bypass TLS certificate validation during firmware updates, enabling the installation of malicious firmware on ASUS routers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rt-ac1900p_firmware","vendor":"asus"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered on ASUS RT-AC1900P routers before 3.0.0.4.385_20253. The router accepts an arbitrary server certificate for a firmware update. The culprit is the --no-check-certificate option passed to wget tool used to download firmware update files.","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":"Security feature bypass in n/a","id":"CVE-2020-15498","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-15499"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-15497"},"products":["n/a"],"published":"2020-08-26","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-15499","kev_date_added":null,"published":"2020-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":"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 bypass TLS certificate validation during firmware updates, enabling the installation of malicious firmware on ASUS routers.","url":"https://insights.sbomify.com/CVE-2020-15498/"}