LOWCVE-2015-3448CVSS 2.5

CVE-2015-3448: Information Disclosure in Ruby Rest-Client

Platform

ruby

Component

rest-client

Fixed in

1.7.3

CVE-2015-3448 affects the Ruby rest-client library, specifically versions up to 1.7.2.rc1. This vulnerability results in the logging of usernames and passwords, potentially exposing sensitive credentials to local users who can access the application's log files. The vulnerability was published in 2017 and a fix is available in version 1.7.3.

Ruby

Detect this CVE in your project

Upload your Gemfile.lock file and we'll tell you instantly if you're affected.

Upload Gemfile.lockSupported formats: Gemfile.lock · Gemfile

Impact and Attack Scenarios

The primary impact of CVE-2015-3448 is the exposure of sensitive credentials. An attacker with local access to the system and the ability to read log files can potentially obtain usernames and passwords used by the application. This could lead to unauthorized access to the application itself or to other systems if the same credentials are reused. While the CVSS score is LOW, the potential for credential theft makes this a significant concern, especially in environments where sensitive data is handled.

Exploitation Context

CVE-2015-3448 is not currently listed on KEV or EPSS. The LOW CVSS score suggests a low probability of active exploitation. Public proof-of-concept (POC) code may exist, but there are no reports of widespread exploitation campaigns targeting this vulnerability. The vulnerability was initially reported and addressed several years ago, reducing the likelihood of ongoing exploitation.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO

EPSS

0.07% (20% percentile)

Affected Software

Componentrest-client
Vendorosv
Maximum version1.7.2.rc1
Fixed in1.7.3

Timeline

  1. Published
  2. Modified
  3. EPSS updated

Mitigation and Workarounds

The recommended mitigation for CVE-2015-3448 is to upgrade to rest-client version 1.7.3 or later. If upgrading is not immediately feasible, consider restricting access to the application's log files to authorized personnel only. Implement a robust logging policy that avoids logging sensitive information like usernames and passwords. Review existing log files for any exposed credentials and rotate them immediately. After upgrading, verify the fix by attempting to trigger a request that would have previously logged credentials and confirming that no sensitive data is now present in the logs.

How to fix

No official patch available. Check for workarounds or monitor for updates.

Frequently asked questions

What is CVE-2015-3448 — Information Disclosure in Ruby Rest-Client?

CVE-2015-3448 is a vulnerability in Ruby rest-client versions up to 1.7.2.rc1 that allows local users to read usernames and passwords from log files, potentially exposing sensitive credentials.

Am I affected by CVE-2015-3448 in Ruby Rest-Client?

You are affected if your application uses rest-client version 1.7.2.rc1 or earlier. Check your gem dependencies to determine if you are using a vulnerable version.

How do I fix CVE-2015-3448 in Ruby Rest-Client?

Upgrade to rest-client version 1.7.3 or later. This resolves the logging of sensitive information. Also, review your logging practices to avoid logging credentials.

Is CVE-2015-3448 being actively exploited?

There are no current reports of widespread exploitation campaigns targeting CVE-2015-3448, but the potential for credential theft remains a concern.

Where can I find the official Ruby Rest-Client advisory for CVE-2015-3448?

Refer to the rest-client gem's release notes and RubyGems.org for information related to this vulnerability: https://rubygems.org/gems/rest-client/versions/1.7.3

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

Ruby

Detect this CVE in your project

Upload your Gemfile.lock file and we'll tell you instantly if you're affected.

Upload Gemfile.lockSupported formats: Gemfile.lock · Gemfile
livefree scan

Scan your Ruby project now — no account

Upload your Gemfile.lock and get the vulnerability report instantly. No account. Uploading the file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...