OpenstackApplication · Redhat
CVE-2013-2029
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 · uneditednagios.upgrade_to_v3.sh, as distributed by Red Hat and possibly others for Nagios Core 3.4.4, 3.5.1, and earlier, allows local users to overwrite arbitrary files via a symlink attack on a temporary nagioscfg file with a predictable name 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 confidenceThe nagios.upgrade_to_v3.sh script creates temporary configuration files in /tmp with predictable, static filenames (nagioscfg). Local users can exploit this by creating a symbolic link with the same predictable name before the script runs, causing the script to overwrite arbitrary files on the system with root privileges during the upgrade process.
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
OpenstackApplication
= 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:N/I:C/A:C
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 if Redhat Openstack 3.0 is installedRun 'rpm -qa | grep -i openstack' or check system package manager for Redhat Openstack version 3.0Affected if The system has Redhat Openstack version 3.0 installed
-
Locate the nagios.upgrade_to_v3.sh scriptSearch for the file using 'find / -name nagios.upgrade_to_v3.sh 2>/dev/null' or check common Nagios installation pathsAffected if The nagios.upgrade_to_v3.sh script is present on the system
-
Inspect the script for predictable temporary file usageRead the script content and search for '/tmp/nagioscfg' or similar predictable filename patterns in temporary file creation logicAffected if The script creates files in /tmp using the static filename 'nagioscfg' or similar predictable names
-
Check script permissions and execution contextRun 'ls -la <path_to_script>' and check if the script is owned by root and has setuid/setgid bits, or if it is invoked with root privileges during upgrade proceduresAffected if The script runs with root or elevated privileges and can be triggered by an upgrade process
A system is affected if it runs Redhat Openstack 3.0 with the nagios.upgrade_to_v3.sh script present and that script uses predictable temporary filenames in /tmp while executing with elevated privileges.
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 dataAvoid running the upgrade script with elevated privileges in multi-user environments. Implement secure temporary file creation using mktemp or private /tmp directories, and upgrade to a patched Nagios version that addresses this vulnerability.
Fix this in Openstack
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2029 — 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-2029 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