Private-key disclosure via weak default file permissions
Published Oct 19, 2022 · Updated May 9, 2025
Incorrect default permissions in Red Hat OpenShift 1 allow local users on a broker server to read its private server key. The installer generates /etc/openshift/server_priv.pem but applies no restrictive file mode, leaving the private key readable through inherited defaults. Exploitation requires local broker access and exposes the private key; no write access or service interruption is reported.
Summary
What happened
Incorrect default permissions in Red Hat OpenShift 1 allow local users on a broker server to read its private server key. The installer generates /etc/openshift/server_priv.pem but applies no restrictive file mode, leaving the private key readable through inherited defaults. Exploitation requires local broker access and exposes the private key; no write access or service interruption is reported.
The record
- CVE
- CVE-2013-4281
- Published
- Oct 19, 2022
- Updated
- May 9, 2025
- Vendor
- Red Hat
- Product
- OpenShift
- Classifications
- CWE-276, T1552.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- May 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Red Hat Openshift 1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo