# CVE-2018-12482: SQL injection in n/a

> Authenticated attackers can exploit SQL injection vulnerabilities in the OCS Inventory search engine to read or modify database contents.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-12482, GHSA-h46q-44pm-ghrg, UBUNTU-CVE-2018-12482

## What is CVE-2018-12482?

CVE-2018-12482 is a high-severity SQL injection vulnerability in n/a, published on 3 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OCS Inventory 2.4.1 contains multiple SQL injections in the search engine. Authentication is needed in order to exploit the issues.

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

## Which versions are affected by CVE-2018-12482?

It affects 1 product.


Products: Ocsinventory-Ng Ocsinventory Ng.

## How do I fix CVE-2018-12482?

Upgrade to a fixed version.

## Is CVE-2018-12482 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14473](https://insights.sbomify.com/CVE-2018-14473/): XML external entity in n/a (critical 9.1)
- [CVE-2018-15537](https://insights.sbomify.com/CVE-2018-15537/): File upload in n/a (high 8.8)
- [CVE-2018-12483](https://insights.sbomify.com/CVE-2018-12483/): Command injection in n/a (high 8.8)
- [CVE-2018-1000558](https://insights.sbomify.com/CVE-2018-1000558/): SQL injection in n/a (medium 6.5)
- [CVE-2018-1000557](https://insights.sbomify.com/CVE-2018-1000557/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12482 and fix it if it is affected.

What it is: CVE-2018-12482 is a high-severity SQL injection vulnerability in n/a, published on 3 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12482 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-2018-12482/ (Markdown: https://insights.sbomify.com/CVE-2018-12482/index.md)
```

## Sources

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

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