# CVE-2019-10135: Deserialization in osbs-client

> Insecure YAML deserialization in osbs-client allows attackers to execute arbitrary code via malicious YAML files.

- **Severity:** High 7.2 (`CVSS:3.0/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:** 11 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f3j5-qrv6-xvc6

## What is CVE-2019-10135?

CVE-2019-10135 is a high-severity unsafe deserialization vulnerability in Red Hat osbs-client, published on 11 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the yaml.load() function in the osbs-client versions since 0.46 before 0.56.1. Insecure use of the yaml.load() function allowed the user to load any suspicious object for code execution via the parsing of malicious YAML files.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Osbs-Client Project Osbs-Client.

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

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

## Is CVE-2019-10135 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10135 is a high-severity unsafe deserialization vulnerability in Red Hat osbs-client, published on 11 Jul 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10135 in the wild and no public exploit code.

Affected product: Red Hat osbs-client. 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-10135/ (Markdown: https://insights.sbomify.com/CVE-2019-10135/index.md)
```

## Sources

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

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