{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26525 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26525 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26525 is a critical SQL injection vulnerability in n/a, published on 2 Oct 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-26525 and fix it if it is affected.\n\nWhat it is: CVE-2020-26525 is a critical SQL injection vulnerability in n/a, published on 2 Oct 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-26525 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-26525/ (Markdown: https://insights.sbomify.com/CVE-2020-26525/index.md)","id":"CVE-2020-26525","markdown":"https://insights.sbomify.com/CVE-2020-26525/index.md","name":"CVE-2020-26525","record":{"aliases":["GHSA-9845-gph5-8ccg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Damstra Smart Asset","requires_auth":"none","summary":"SQL injection in Damstra Smart Asset allows attackers to force database connections to external DNS servers, potentially leading to data exposure.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smart_asset","vendor":"damstratechnology"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Damstra Smart Asset 2020.7 has SQL injection via the API/api/Asset originator parameter. This allows forcing the database and server to initiate remote connections to third party DNS servers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-10-02","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-10-02T07:12:18Z","kind":"github_poc","ref":"https://github.com/lukaszstu/SmartAsset-SQLinj-CVE-2020-26525","stars":1,"title":"Damstra Smart Asset 2020.7 has SQL injection via the API/api/Asset originator parameter."}],"tier":"poc_unverified"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2020-26525","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-26526"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-26524"},"products":["n/a"],"published":"2020-10-02","related":[{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2020-26527","kev_date_added":null,"published":"2020-10-02"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2020-26526","kev_date_added":null,"published":"2020-10-02"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"SQL injection in Damstra Smart Asset allows attackers to force database connections to external DNS servers, potentially leading to data exposure.","url":"https://insights.sbomify.com/CVE-2020-26525/"}