CVE-2016-6345: Exposure of Sensitive Information to an Unauthorized Actor in RESTEasy

Summary

17/05/2022
Yes i
Moderate
6.5

CVE-2016-6345: Exposure of Sensitive Information to an Unauthorized Actor in RESTEasy. Affects org.jboss.resteasy:resteasy-client across 2 version ranges.

< 3.0.20.Final >= 3.1.0.Beta1, < 3.1.0.CR1

Fixed in 3.0.20.Final or 3.1.0.CR1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2016-6345 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The RESTEasy package is a Java framework that provides a set of tools and utilities for building RESTful web services. It is commonly used in Maven projects and offers features such as client and server implementations, support for various HTTP methods, and handling of JSON and XML payloads. However, versions up to 3.0.19.Final and 3.1.0.Beta2 of the 'org.jboss.resteasy:resteasy-client' package are vulnerable to an exposure of sensitive information issue.

Vulnerability Detail

The vulnerability arises due to the insufficient use of random values in async jobs within RESTEasy. This flaw allows remote authenticated users to obtain sensitive information. An attacker can exploit this vulnerability to gain unauthorized access to sensitive data, potentially leading to further attacks or unauthorized actions. The Common Vulnerabilities and Exposures (CVE) identifier for this vulnerability is CVE-2016-6345. The vulnerability has a CVSSv3 score of 6.5, indicating a moderate severity level.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 3.0.20.Final 3.0.20.Final
  • >= 3.1.0.Beta1, < 3.1.0.CR1 3.1.0.CR1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed versions as mentioned in the 'how_to_fix' section.

Conclusion

In conclusion, the 'org.jboss.resteasy:resteasy-client' package versions up to 3.0.19.Final and 3.1.0.Beta2 are vulnerable to an exposure of sensitive information issue. It is crucial to update to the fixed versions (3.0.20.Final or higher for versions up to 3.0.19.Final, and 3.1.0.CR1 or higher for versions up to 3.1.0.Beta2) to mitigate the vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for org.jboss.resteasy:resteasy-client →

Share this vulnerability

FAQ

RESTEasy is a Java framework for building RESTful web services. It provides tools and utilities to simplify the development of RESTful APIs.

The vulnerability allows remote authenticated users to access sensitive information. This can lead to unauthorized access, data breaches, or further attacks.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it for vulnerabilities in real-time.

No, there are no known workarounds for this vulnerability. Updating to the fixed versions is the recommended solution.

The vulnerability has a CVSSv3 score of 6.5, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for org.jboss.resteasy:resteasy-client.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 3.0.20.Final 3.0.20.Final
  • >= 3.1.0.Beta1, < 3.1.0.CR1 3.1.0.CR1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback