OpenshiftApplication · Redhat
CVE-2013-0163
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 · uneditedOpenShift haproxy cartridge: predictable /tmp in set-proxy connection hook which could facilitate DoS
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 confidenceThe OpenShift haproxy cartridge's set-proxy connection hook uses predictable filenames in /tmp, allowing an attacker to potentially interfere with or disrupt the proxy connection setup, leading to a denial of service condition.
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
= 1.0= 2.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify OpenShift versionRun 'oo-version' or check /etc/openshift/env/OPENSHIFT_VERSION if available, or look for version file in the OpenShift installation directoryAffected if Version is 1.0 or 2.0 (exact match)
-
Locate haproxy cartridge installationFind the haproxy cartridge directory - typically in /usr/lib/openshift/cartridges/haproxy or /var/lib/openshift/cartridges/haproxyAffected if haproxy cartridge is installed on the system
-
Inspect set-proxy connection hookLocate the set-proxy script within the haproxy cartridge - look for files named set-proxy, proxy, or connection-related hooks in the cartridge's bin or hooks directoryAffected if The script exists and uses hardcoded/predictable filenames in /tmp instead of mktemp or UUID-based naming
-
Check /tmp for predictable haproxy filesList files in /tmp directory and look for any haproxy-related files with predictable naming patterns (e.g., sequential or static filenames)Affected if Files matching predictable patterns exist in /tmp related to haproxy proxy setup
-
Verify hook execution contextExamine how the set-proxy hook is invoked - check if it's triggered during connection setup for applications using the haproxy cartridgeAffected if Applications are configured to use the haproxy cartridge with connection hooks enabled
Environment is affected if running OpenShift version 1.0 or 2.0 with the haproxy cartridge installed and the set-proxy hook uses predictable /tmp filenames.
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 dataModify the set-proxy connection hook to use unpredictable file paths (e.g., via mktemp or UUID-based naming) instead of predictable /tmp filenames.
Fix this in Openshift
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0163 — 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-2013-0163 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