# CVE-2019-17315: Deserialization in n/a

> An admin user can achieve code execution via PHP object injection in the SugarCRM Administration module.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-75mv-gp69-2cqm

## What is CVE-2019-17315?

CVE-2019-17315 is a high-severity unsafe deserialization vulnerability in Sugarcrm Sugarcrm, published on 7 Oct 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SugarCRM before 8.0.4 and 9.x before 9.0.2 allows PHP object injection in the Administration module by an Admin user.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2019-17315?

It affects 1 product.


Products: Sugarcrm Sugarcrm.

## How do I fix CVE-2019-17315?

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

## Is CVE-2019-17315 being exploited?

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

## Other vulnerabilities in Sugarcrm Sugarcrm

- [CVE-2023-22952](https://insights.sbomify.com/CVE-2023-22952/): Multiple SugarCRM Products Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2004-1225](https://insights.sbomify.com/CVE-2004-1225/): SQL injection in n/a (critical 10.0)
- [CVE-2020-7472](https://insights.sbomify.com/CVE-2020-7472/): Path traversal in n/a (critical 9.8)
- [CVE-2012-0694](https://insights.sbomify.com/CVE-2012-0694/): Deserialization in n/a (critical 9.8)
- [CVE-2014-3244](https://insights.sbomify.com/CVE-2014-3244/): XML external entity in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17315 and fix it if it is affected.

What it is: CVE-2019-17315 is a high-severity unsafe deserialization vulnerability in Sugarcrm Sugarcrm, published on 7 Oct 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17315 in the wild and no public exploit code.

Affected product: Sugarcrm Sugarcrm. 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-2019-17315/ (Markdown: https://insights.sbomify.com/CVE-2019-17315/index.md)
```

## Sources

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

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