# CVE-2017-15378: SQL injection in n/a

> SQL injection in the E-Sic password reset parameter allows attackers 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:** No
- **Published:** 23 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v2q5-6v56-46r3

## What is CVE-2017-15378?

CVE-2017-15378 is a high-severity SQL injection vulnerability in n/a, published on 23 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL Injection exists in the E-Sic 1.0 password reset parameter (aka the cpfcnpj parameter to the /reset URI).

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

## Which versions are affected by CVE-2017-15378?

It affects 1 product.


Products: Softwarepublico E-Sic.

## How do I fix CVE-2017-15378?

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

## Is CVE-2017-15378 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15379](https://insights.sbomify.com/CVE-2017-15379/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-15381](https://insights.sbomify.com/CVE-2017-15381/): SQL injection in n/a (critical 9.8)
- [CVE-2017-15373](https://insights.sbomify.com/CVE-2017-15373/): SQL injection in n/a (critical 9.8)
- [CVE-2017-15380](https://insights.sbomify.com/CVE-2017-15380/): XSS exists in the E-Sic 1.0 /cadastro/index.php URI (aka the requester's registration area) via the nome parameter. (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15378 and fix it if it is affected.

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

## Sources

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

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