OpenshiftApplication · Redhat
CVE-2015-5305
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDirectory traversal vulnerability in Kubernetes, as used in Red Hat OpenShift Enterprise 3.0, allows attackers to write to arbitrary files via a crafted object type name, which is not properly handled before passing it to etcd.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDirectory traversal vulnerability in Kubernetes affecting Red Hat OpenShift Enterprise 3.0. Attackers can write to arbitrary files on the host system by providing a crafted object type name that is not properly sanitized before being passed to etcd, allowing path traversal characters to be interpreted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpenshiftApplication
= 3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm OpenShift Enterprise versionRun 'oc version' or 'openshift version' to retrieve the installed OpenShift version. Check the output against the affected version 3.0.Affected if The installed version is OpenShift Enterprise 3.0 exactly.
-
Verify Kubernetes API server is accessibleCheck if the Kubernetes API server (kube-apiserver) is running by querying the API endpoint, typically on port 8443 or 6443. Use 'curl -k https://<api-server>:8443/api' or check process status.Affected if The Kubernetes API server is running and accessible.
-
Confirm etcd is in useCheck if etcd is running as the backend data store for OpenShift. Look for etcd process (ps aux | grep etcd) or check the OpenShift master configuration for etcd connection details.Affected if etcd is running and configured as the data store.
-
Check for exposed Kubernetes APIDetermine if the Kubernetes API is network-accessible to untrusted users or if anonymous access is enabled. Review the API server configuration and network policies.Affected if The API server accepts requests from untrusted sources or anonymous users.
The environment is affected if OpenShift Enterprise version 3.0 is running with the Kubernetes API server and etcd accessible, allowing crafted object type names to reach etcd storage.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply available security patches for Kubernetes and Red Hat OpenShift Enterprise 3.0 that address input validation of object type names before etcd operations. Implement strict validation/sanitization of object type names to prevent path traversal.
Fix this in Openshift
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5305 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data