Security readout for executives and security teams
Plain-English summary
CVE-2019-10135 affects Red Hat osbs-client versions 0.46 through before 0.56.1. A malicious YAML file could cause code execution when parsed. This is serious for build or container automation environments, but the source bundle does not show active exploitation.
Executive priority
Prioritize remediation for build infrastructure, CI/CD systems, and container build environments. The business risk is unauthorized code execution inside trusted automation, though public evidence here does not show active exploitation.
Technical view
The issue is unsafe deserialization through yaml.load() in osbs-client, mapped to CWE-502. The CVSS 3.0 score is 7.2 with network attack vector, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where osbs-client versions since 0.46 before 0.56.1 process YAML supplied by privileged users, build workflows, automation, or repository-controlled inputs.
Exploitation context
The provided sources do not indicate KEV listing or active exploitation. Successful abuse appears to require high privileges and the ability to influence YAML parsed by vulnerable osbs-client code.
Researcher notes
The source bundle establishes affected versions, root cause, CWE, and CVSS. It does not provide exploit samples, observed exploitation, or detailed environmental preconditions beyond malicious YAML parsing and high privileges.
Mitigation direction
- Upgrade osbs-client to 0.56.1 or a later vendor-supported fixed version.
- Check Red Hat and upstream osbs-client guidance for distribution-specific fixed packages.
- Avoid processing untrusted YAML with vulnerable osbs-client versions.
- For maintained forks, replace unsafe yaml.load() use with safe YAML parsing.
Validation and detection
- Inventory systems and build environments for osbs-client installations.
- Confirm installed osbs-client versions are not 0.46 through before 0.56.1.
- Review build jobs for YAML inputs processed by osbs-client.
- Check SBOMs, lockfiles, and container images for vulnerable osbs-client versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-10135 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.2HighVector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10135CVE reference
- https://github.com/containerbuildsystem/osbs-client/pull/865CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.