# CVE-2017-18375: Deserialization in n/a

> Ampache allows PHP object instantiation via specific AJAX endpoints, potentially enabling remote code execution.

- **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:** 24 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p3j4-f85x-cw86, UBUNTU-CVE-2017-18375

## What is CVE-2017-18375?

CVE-2017-18375 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ampache 3.8.3 allows PHP Object Instantiation via democratic.ajax.php and democratic.class.php.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Ampache Ampache.

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

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

## Is CVE-2017-18375 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-0606](https://insights.sbomify.com/CVE-2023-0606/): Cross-site Scripting (XSS) - Reflected in ampache/ampache (critical 9.3)
- [CVE-2021-21399](https://insights.sbomify.com/CVE-2021-21399/): Unauthenticated SubSonic backend access in Ampache (critical 9.1)
- [CVE-2019-12385](https://insights.sbomify.com/CVE-2019-12385/): SQL injection in n/a (high 8.8)
- [CVE-2020-15153](https://insights.sbomify.com/CVE-2020-15153/): Unauthenticated SQL injection in Ampache (high 8.2)
- [CVE-2006-5668](https://insights.sbomify.com/CVE-2006-5668/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18375 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 May 2019. 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-18375 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-18375/ (Markdown: https://insights.sbomify.com/CVE-2017-18375/index.md)
```

## Sources

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

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