dbcve.org
ResteasyApplication · Redhat

CVE-2016-6345

MEDIUM · 6.5 CVSS v3.0 Published 2016-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
RESTEasy allows remote authenticated users to obtain sensitive information by leveraging "insufficient use of random values" in async jobs.

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 · moderate confidence

RESTEasy's async job implementation uses insufficient randomness when generating identifiers or tokens for asynchronous jobs, allowing authenticated users to potentially guess or predict these values and access sensitive information associated with other users' async jobs.

MitigationUpgrade RESTEasy to a version that implements cryptographically strong random values for async job identifiers. Review async job implementations to identify and protect sensitive data paths.

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
Affected:all versions

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

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

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. Identify RESTEasy library presence
    Search for resteasy*.jar files in your application classpath, lib directories, or dependency manifests (pom.xml, build.gradle). Look for packages starting with org.jboss.resteasy or javax.ws.rs
    Affected if RESTEasy libraries are found in the application runtime
  2. Confirm async job functionality is in use
    Inspect application code for imports of async-related classes such as javax.ws.rs.container.AsyncResponse, or resteasy.async.* classes. Check for @Suspended annotations on JAX-RS resource methods or programmatic use of AsyncResponse
    Affected if The application uses AsyncResponse or other RESTEasy async job mechanisms
  3. Verify async endpoint exposure
    Review JAX-RS resource endpoints that use async processing. Check web.xml or application configuration for async-supported servlet mappings. Look for patterns like @GET with @Suspended AsyncResponse parameter
    Affected if There are exposed REST endpoints using async job processing
  4. Check for job ID or token generation
    Search source code for methods that generate identifiers for async jobs, such as calls to java.util.Random, java.lang.Math.random(), or custom ID generation logic within async job handlers
    Affected if Custom or weak random generation is used for async job identifiers rather than java.security.SecureRandom
  5. Review async job data sensitivity
    Examine what data is associated with async job identifiers. Check if job results, status, or retrieved data contain sensitive information tied to the job ID/token
    Affected if Async jobs store or return sensitive data that can be accessed by knowledge of the job identifier

If RESTEasy with async job processing is in use, the application is affected since all versions of Red Hat RESTEasy have insufficient randomness in async job identifier generation, allowing unauthorized access to other users' async job data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade RESTEasy to a version that implements cryptographically strong random values for async job identifiers. Review async job implementations to identify and protect sensitive data paths.

Fix this in Resteasy 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-6345 — 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-6345 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