ResteasyApplication · Redhat
CVE-2018-1051
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIt was found that the fix for CVE-2016-9606 in versions 3.0.22 and 3.1.2 was incomplete and Yaml unmarshalling in Resteasy is still possible via `Yaml.load()` in YamlProvider.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRESTEasy's YamlProvider contains an incomplete fix for CVE-2016-9606, where the unsafe Yaml.load() method is still used for YAML unmarshalling. This allows attackers to craft malicious YAML payloads that can trigger arbitrary object instantiation and potentially execute arbitrary code through deserialization attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ResteasyApplication
= 3.0.22= 3.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify RESTEasy installation and versionSearch for resteasy-core jar files or check Maven/Gradle dependencies for resteasy version. Common locations: WEB-INF/lib, .m2/repository, or build configuration files.Affected if Version equals 3.0.22 or 3.1.2 exactly
-
Locate YamlProvider class in the applicationSearch for YamlProvider.java or YamlProvider.class within the resteasy-yaml or resteasy-jaxrs library files. Check the source code for the YAML parsing implementation.Affected if YamlProvider exists and uses Yaml.load() instead of Yaml.safe_load() for unmarshalling
-
Verify YAML input processing is enabledCheck if YAML content types (application/x-yaml, text/yaml) are accepted by REST endpoints or if YamlProvider is registered as a MessageBodyReader in the deployment configuration.Affected if REST endpoints accept YAML content and YamlProvider is actively handling deserialization
-
Inspect YAML parsing implementationExamine the YamlProvider source or bytecode for the load() method call. Look for: new Yaml().load() or Yaml.load() without the safe_load() variant.Affected if Code contains Yaml.load() call without safe_load() or safe loading configuration
You are affected if RESTEasy version is exactly 3.0.22 or 3.1.2 AND your application processes YAML input through YamlProvider using the unsafe Yaml.load() method.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade RESTEasy to the version where this vulnerability is fully addressed, or replace Yaml.load() with the safer Yaml.safe_load() method and validate all YAML input before processing.
Fix this in Resteasy
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1051 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data