dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2016-7050

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SerializableProvider in RESTEasy in Red Hat Enterprise Linux Desktop 7, Red Hat Enterprise Linux HPC Node 7, Red Hat Enterprise Linux Server 7, and Red Hat Enterprise Linux Workstation 7 allows remote attackers to execute arbitrary code.

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 confidence

RESTEasy's SerializableProvider contains an unsafe deserialization vulnerability that allows remote attackers to send specially crafted serialized Java objects through the RESTEasy endpoint, leading to arbitrary code execution on the target system. This is a classic Java deserialization flaw where untrusted serialized data is processed without proper validation.

MitigationApply the vendor-supplied patches for Red Hat Enterprise Linux 7 to update RESTEasy to a fixed version. If patches are unavailable, disable or remove the SerializableProvider and implement network-level restrictions to limit exposure to untrusted clients.

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
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux Hpc NodeOperating system
Affected:= 7.0
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 7.0

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if RESTEasy packages are installed
    Run 'rpm -qa | grep -i resteasy' or 'rpm -qa | grep -i jboss' to list installed RESTEasy or JBoss packages
    Affected if No RESTEasy packages are found, the system is not affected by this specific vulnerability
  2. Identify the exact RESTEasy version
    Run 'rpm -qi <package-name>' on the RESTEasy package found, or use 'rpm -qa | grep resteasy' to get version information
    Affected if The installed RESTEasy version matches the vulnerable version bundled with RHEL 7.0 (exact version depends on the RHEL 7.0 repository state at time of installation)
  3. Verify the SerializableProvider class exists
    Search for the SerializableProvider class in the RESTEasy jar files: 'find /usr -name "*.jar" -path "*resteasy*" -exec unzip -l {} \; 2>/dev/null | grep -i SerializableProvider'
    Affected if The SerializableProvider class is present in the RESTEasy installation, indicating the vulnerable component is available
  4. Check for exposed RESTEasy web service endpoints
    Inspect deployed WAR files or REST endpoint configurations in /var/lib/jbossas or /usr/share/resteasy directories, and check configuration files (web.xml, resteasy-config.xml) for registered providers
    Affected if RESTEasy endpoints are exposed and the SerializableProvider is registered as a provider in the configuration

A system is affected if it runs RHEL 7.0 with RESTEasy installed and the SerializableProvider class is present in a deployed configuration, allowing deserialization of untrusted data through REST endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches for Red Hat Enterprise Linux 7 to update RESTEasy to a fixed version. If patches are unavailable, disable or remove the SerializableProvider and implement network-level restrictions to limit exposure to untrusted clients.

Recommended fix High confidence

Latest RHEL 7.0 security errata via yum update (specific RHSA patch from Red Hat)

  1. Ensure the system is registered with Red Hat Subscription Management or RHN (redhat-register)
  2. Run 'yum check-update' to check for available security updates
  3. Apply the security update for RESTEasy: yum update(resteasy*) or yum update to get all available security patches
  4. Restart any services or applications using RESTEasy after the update (systemctl restart <service>)
  5. Verify the updated packages are installed: rpm -qa | grep resteasy
Caveat Standard risk of any system update - test in staging first; minor risk of application compatibility changes with updated libraries

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-7050 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-7050 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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