Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-9593

foreman-debug: missing obfuscation of sensitive information

Overview

Published
16 Apr 2018
Modified
17 Jun 2026
High CVE
0 Registry packages
110 OS packages
1 Linux distributions
Yes Fix available

Description

foreman-debug before version 1.15.0 is vulnerable to a flaw in foreman-debug's logging. An attacker with access to the foreman log file would be able to view passwords, allowing them to access those systems.

Source: OX vulnerability database

Severity

8.8 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Weakness: CWE-522, CWE-255

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 65 fixes

Red Hat 1 release · 65 packages

fixed 65
rubygem-kafo-wizards tfm-rubygem-hammer-cli-foreman-tasks rubygem-smart-proxy-dhcp-remote-isc tfm-rubygem-hammer-cli-foreman-virt-who-configure tfm-rubygem-hammer-cli-foreman-remote-execution tfm-rubygem-hammer-cli-foreman-docker +59
Red Hat fixes for CVE-2016-9593
ReleasePackageFixed inAdvisory
7 rubygem-kafo-wizards 0:0.0.1-2.el7sat RHSA-2018:0336
7 tfm-rubygem-hammer-cli-foreman-tasks 0:0.0.12-1.fm1_15.el7sat RHSA-2018:0336
7 rubygem-smart-proxy-dhcp-remote-isc 0:0.0.2.1-1.fm1_15.el7sat RHSA-2018:0336
7 tfm-rubygem-hammer-cli-foreman-virt-who-configure 0:0.0.3-1.el7sat RHSA-2018:0336
7 tfm-rubygem-hammer-cli-foreman-remote-execution 0:0.0.6-1.fm1_15.el7sat RHSA-2018:0336
7 tfm-rubygem-hammer-cli-foreman-docker 0:0.0.6-2.el7sat RHSA-2018:0336

59 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.