CVE-2023-4886VulnerabilityPublished 3 Oct 2023Updated 20 Nov 2025

CVE-2023-4886: Red Hat Satellite 6.13 for RHEL 8 · Information Exposure

Affects Red Hat Satellite 6.13 for RHEL 8Source CVE Database V5

Not known to be exploited · CVSS 6.7 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Oct 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2023-4886, organizations should immediately audit the file permissions of the tomcat server.xml file on all Red Hat Satellite 6.13 installations running on RHEL 8. The file should be restricted to only the necessary system users and groups, typically the tomcat or foreman service accounts, removing world-readable permissions. Implement strict access controls and monitoring on the Satellite server to detect unauthorized access attempts. Review and limit the number of users with high privileges on the system to reduce insider threat risks. Apply any patches or updates released by Red Hat addressing this vulnerability as soon as they become available. Additionally, rotate the keystore and truststore passwords after remediation to invalidate any potentially exposed credentials. Employ host-based intrusion detection systems (HIDS) to monitor changes to critical configuration files. Finally, conduct regular security training for administrators managing Red Hat Satellite to ensure secure configuration practices are followed.

Description

A sensitive information exposure vulnerability was found in foreman. Contents of tomcat's server.xml file, which contain passwords to candlepin's keystore and truststore, were found to be world readable.

Impact

For European organizations, the exposure of keystore and truststore passwords in Red Hat Satellite can have serious consequences. Confidentiality is compromised as attackers or unauthorized users can obtain sensitive credentials, potentially allowing them to impersonate or manipulate subscription services. Integrity is at risk because attackers could alter entitlement data or interfere with the management of Red Hat subscriptions, leading to unauthorized software usage or denial of legitimate licenses. Availability could also be affected if attackers disrupt subscription services or cause failures in the Satellite infrastructure. Organizations with complex Red Hat environments, especially those in regulated sectors such as finance, healthcare, and critical infrastructure, may face compliance violations and operational disruptions. The requirement for local privileged access limits remote exploitation but increases the risk from insider threats or attackers who have already gained elevated access. The lack of known exploits reduces immediate risk but does not eliminate the potential for targeted attacks. Overall, the vulnerability could undermine trust in subscription management and increase the attack surface within enterprise Linux environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 20 Nov 2025, 19:03 UTC

Technical details

References

Community reviews

Related threats