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

> An attacker can bypass authentication and inject SQL via malformed array parameters in the Cookie header, gaining unauthorized access to the application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fm6v-5q4c-8xxp

## What is CVE-2020-25132?

CVE-2020-25132 is a critical SQL injection vulnerability in n/a, published on 25 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to SQL Injection due to the fact that it is possible to inject malicious SQL statements in malformed parameter types. Sending the improper variable type Array allows a bypass of core SQL Injection sanitization. Users are able to inject malicious statements in multiple functions. This vulnerability leads to full authentication bypass: any unauthorized user with access to the application is able to exploit this vulnerability. This can occur via the Cookie header to the default URI, within includes/authenticate.inc.php.

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

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

It affects 1 product.


Products: Observium Observium.

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

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

## Is CVE-2020-25132 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25147](https://insights.sbomify.com/CVE-2020-25147/): SQL injection in n/a (critical 9.8)
- [CVE-2020-25133](https://insights.sbomify.com/CVE-2020-25133/): Path traversal in n/a (high 8.8)
- [CVE-2020-25134](https://insights.sbomify.com/CVE-2020-25134/): Path traversal in n/a (high 8.8)
- [CVE-2020-25136](https://insights.sbomify.com/CVE-2020-25136/): Path traversal in n/a (high 8.8)
- [CVE-2020-25143](https://insights.sbomify.com/CVE-2020-25143/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25132 is a critical SQL injection vulnerability in n/a, published on 25 Sep 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-25132 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-25132/ (Markdown: https://insights.sbomify.com/CVE-2020-25132/index.md)
```

## Sources

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

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