dbcve.org
OpenshiftApplication · Redhat

CVE-2013-0165

HIGH · 7.3 CVSS v3.1 Published 2019-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
cartridges/openshift-origin-cartridge-mongodb-2.2/info/bin/dump.sh in OpenShift does not properly create files in /tmp.

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 · high confidence

The MongoDB cartridge's dump.sh script creates temporary files in /tmp without proper security measures, likely using predictable filenames or insecure methods. This could allow local attackers to perform symlink attacks or race condition exploits to overwrite arbitrary files or escalate privileges.

MitigationReplace insecure /tmp file creation with secure methods such as using 'mktemp' command or proper file descriptors, and ensure appropriate file permissions are set on temporary files.

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
Affected:all versions

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if OpenShift environment is deployed
    Verify whether Red Hat OpenShift is installed in your environment by checking for the 'oo' command-line tools or looking for OpenShift-related processes and services.
    Affected if OpenShift is deployed and the MongoDB cartridge is in use
  2. Locate the MongoDB cartridge dump.sh script
    Find the dump.sh script within the MongoDB cartridge directory. Common paths include /usr/libexec/openshift/cartridges/mongodb/bin/ or similar cartridge-specific directories under the OpenShift installation root.
    Affected if The dump.sh script exists in the MongoDB cartridge
  3. Inspect dump.sh for /tmp temporary file creation
    Open the dump.sh script and search for commands that create files in /tmp, such as redirection to /tmp/filename or using '>' with /tmp paths. Look for patterns like '/tmp/' in the script content.
    Affected if The script contains commands creating temporary files in /tmp
  4. Verify if secure temporary file methods are used
    Check whether the script uses secure methods like 'mktemp', file descriptors with 'trap', or other secure temporary file creation mechanisms. Look for absence of 'mktemp' or proper file descriptor usage.
    Affected if The script does NOT use mktemp or secure file descriptors for temporary files and instead uses predictable filenames in /tmp
  5. Check /tmp directory permissions and attack surface
    Examine /tmp directory permissions (ls -ld /tmp) and look for any world-writable permissions that would allow symlink attacks. Check if multiple OpenShift users or applications have access to the same environment.
    Affected if The /tmp directory has permissive permissions allowing symlink or race condition attacks

Your environment is affected if OpenShift with the MongoDB cartridge is deployed and the dump.sh script creates temporary files in /tmp using insecure methods without mktemp or proper file descriptors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace insecure /tmp file creation with secure methods such as using 'mktemp' command or proper file descriptors, and ensure appropriate file permissions are set on temporary files.

Fix this in Openshift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0165 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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