# CVE-2020-26525: SQL injection in n/a

> SQL injection in Damstra Smart Asset allows attackers to force database connections to external DNS servers, potentially leading to data exposure.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9845-gph5-8ccg

## What is CVE-2020-26525?

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.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-26525?

It affects 1 product.


Products: Damstratechnology Smart Asset.

## How do I fix CVE-2020-26525?

No fix has been published for CVE-2020-26525 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-26525 being exploited?

There is no known exploitation of CVE-2020-26525 in the wild and no public exploit code.

Public exploit code:

- Damstra Smart Asset 2020.7 has SQL injection via the API/api/Asset originator parameter. (github_poc): https://github.com/lukaszstu/SmartAsset-SQLinj-CVE-2020-26525

## Other vulnerabilities in n/a

- [CVE-2020-26527](https://insights.sbomify.com/CVE-2020-26527/): Misconfiguration in n/a (critical 9.8)
- [CVE-2020-26526](https://insights.sbomify.com/CVE-2020-26526/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26525 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2020-26525 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26525/ (Markdown: https://insights.sbomify.com/CVE-2020-26525/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26525
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26525
- OSV: https://osv.dev/vulnerability/CVE-2020-26525

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26525/
Summaries are generated and may contain mistakes; the official description above is the record.