CVE-2012-0433
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 · uneditedThe install-chef-suse.sh script shipped with crowbar before 2012-10-02 is creating files containing confidential data with insecure permissions, allowing local users to read confidential data.
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 install-chef-suse.sh script in Crowbar creates files containing confidential data (such as credentials, keys, or configuration data) with overly permissive file permissions (likely world-readable), allowing any local user on the system to read sensitive information that should be protected.
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<= 1.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check if Crowbar is installedLook for Crowbar installation directories or the presence of the install-chef-suse.sh script in common locations such as /opt/crowbar, /root/crowbar, or the original installation mediaAffected if Crowbar version 1.0 or earlier is found on the system
-
Locate the install-chef-suse.sh scriptSearch for the file named install-chere-suse.sh in the Crowbar installation directory or in the path where installation scripts are storedAffected if The script exists on the system and is from Crowbar <= 1.0
-
Examine script for weak file permission patternsOpen the script and search for file creation commands (such as tee, cat, echo redirection, or write operations) that occur without setting restrictive permissions. Look for absence of 'umask 077', 'chmod 600', or similar restrictive permission settings before sensitive file creationAffected if The script creates files containing credentials, keys, or configuration data without enforcing restrictive permissions (chmod 600/700 or umask 077)
-
Check existing sensitive files for world-readable permissionsIdentify files created by install-chef-suse.sh that may contain confidential data (credentials, keys, configuration). Use 'ls -la <filename>' to check permissions. Look for files where the 'others' column shows 'r--' or 'r--' instead of '---'Affected if Any file containing sensitive data created by this script has permissions that allow reading by other users (e.g., -rw-r--r-- or similar world-readable modes)
If Crowbar <= 1.0 is installed and the install-chef-suse.sh script has been executed, check whether sensitive files created by that script have world-readable permissions (anyone can read them), which would indicate the vulnerability is present.
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 dataUpdate the script to set restrictive permissions (e.g., umask 077 or explicit chmod 600) when creating files containing confidential data, and audit any existing files created by this script for exposure.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0433 — 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-2012-0433 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