Skip to content
Noroxi
CVE-2016-9606· NVD / CVE Program· CNA redhat

JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untr

JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions.

HighCVSS 8.1 · v3.0—No exploit Fix available
Published
Mar 9, 2018
Updated
Jun 16, 2026
EPSS
6.0% · 93th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 6.0%

Affected systems

VendorProduct
redhatresteasy

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redhat resteasyup to 3.1.1 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat, Inc. RESTEasy

    • 3.1.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12resteasy3.0before 3.0.26-13.0.26-1
Mavenorg.jboss.resteasy:resteasy-bombefore 3.1.2.Final3.1.2.Final
Red Hat:jboss_enterprise_application_platform:6::el5hibernate4-core-eap6before 0:4.2.26-1.Final_redhat_1.1.ep6.el50:4.2.26-1.Final_redhat_1.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5hibernate4-eap6before 0:4.2.26-1.Final_redhat_1.1.ep6.el50:4.2.26-1.Final_redhat_1.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5hibernate4-entitymanager-eap6before 0:4.2.26-1.Final_redhat_1.1.ep6.el50:4.2.26-1.Final_redhat_1.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5hibernate4-envers-eap6before 0:4.2.26-1.Final_redhat_1.1.ep6.el50:4.2.26-1.Final_redhat_1.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5hibernate4-infinispan-eap6before 0:4.2.26-1.Final_redhat_1.1.ep6.el50:4.2.26-1.Final_redhat_1.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5hornetqbefore 0:2.3.25-20.SP18_redhat_1.1.ep6.el50:2.3.25-20.SP18_redhat_1.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5httpserverbefore 0:1.0.8-1.Final_redhat_1.1.ep6.el50:1.0.8-1.Final_redhat_1.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-common-api-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-common-impl-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-common-spi-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-core-api-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-core-impl-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-deployers-common-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-jdbc-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-spec-api-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5ironjacamar-validator-eap6before 0:1.0.38-3.Final_redhat_3.1.ep6.el50:1.0.38-3.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5jboss-as-appclientbefore 0:7.5.15-1.Final_redhat_3.1.ep6.el50:7.5.15-1.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5jboss-as-clibefore 0:7.5.15-1.Final_redhat_3.1.ep6.el50:7.5.15-1.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5jboss-as-client-allbefore 0:7.5.15-1.Final_redhat_3.1.ep6.el50:7.5.15-1.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5jboss-as-clusteringbefore 0:7.5.15-1.Final_redhat_3.1.ep6.el50:7.5.15-1.Final_redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5jboss-as-cmpbefore 0:7.5.15-1.Final_redhat_3.1.ep6.el50:7.5.15-1.Final_redhat_3.1.ep6.el5

+96

Other highest-scoring records for the same primary product.

  • CVE-2018-1051It 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
    32Monitor
  • CVE-2016-6346RESTEasy enables GZIPInterceptor, which allows remote attackers to cause a denial of service via unspecified vectors.
    32Monitor
  • CVE-2020-1695A flaw was found in all resteasy 3.x.x versions prior to 3.12.0.Final and all resteasy 4.x.x versions prior to 4.6.0.Final, where an imprope
    31Monitor
  • CVE-2016-6345RESTEasy allows remote authenticated users to obtain sensitive information by leveraging "insufficient use of random values" in async jobs.
    27Monitor
  • CVE-2014-7839DocumentProvider in RESTEasy 2.3.7 and 3.0.9 does not configure the (1) external-general-entities or (2) external-parameter-entities feature
    26Monitor
  • CVE-2016-6347Cross-site scripting (XSS) vulnerability in the default exception handler in RESTEasy allows remote attackers to inject arbitrary web script
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:resteasy3.03.0.26-1 · Debian:12Package registry (OSV)
Maven:org.jboss.resteasy:resteasy-bom3.1.2.FinalPackage registry (OSV)
red hat:hibernate4-core-eap60:4.2.26-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:hibernate4-eap60:4.2.26-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:hibernate4-entitymanager-eap60:4.2.26-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:hibernate4-envers-eap60:4.2.26-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:hibernate4-infinispan-eap60:4.2.26-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:hornetq0:2.3.25-20.SP18_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:httpserver0:1.0.8-1.Final_redhat_1.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:ironjacamar-common-api-eap60:1.0.38-3.Final_redhat_3.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:ironjacamar-common-impl-eap60:1.0.38-3.Final_redhat_3.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:ironjacamar-common-spi-eap60:1.0.38-3.Final_redhat_3.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:ironjacamar-core-api-eap60:1.0.38-3.Final_redhat_3.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)
red hat:ironjacamar-core-impl-eap60:1.0.38-3.Final_redhat_3.1.ep6.el7 · Red Hat:jboss_enterprise_application_platform:6::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records