CVE-2010-3912
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 supportconfig script in supportutils in SUSE Linux Enterprise 11 SP1 and 10 SP3 does not "disguise passwords" in configuration files, which has unknown impact and attack vectors.
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 supportconfig utility in SUSE Linux Enterprise 11 SP1 and 10 SP3 fails to properly obfuscate or redact passwords from configuration files when generating support bundles. This causes sensitive credentials to be included in plain text within support output 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= 10= 11CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/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.
-
Verify supportconfig utility is installedRun 'rpm -q supportutils' or 'which supportconfig' to check if the supportconfig package is present on the systemAffected if The package is not installed - the system is not vulnerable to this specific flaw since the utility must be present to generate the exposed bundles
-
Locate generated support bundle filesSearch for support bundle directories, typically found in /var/log/ or /root/ with names like 'supportconfig*' or 'support-*' directories, or files with '.tbz' or '.txt' extensions created by supportconfigAffected if No support bundles exist - the vulnerability only manifests when supportconfig has been executed to generate output files
-
Inspect support bundle contents for plaintext credentialsExtract and examine the support bundle files (e.g., 'tar -xjf *.tbz' or view .txt files) and search configuration files (e.g., /etc/*, *.conf, *.ini, *.xml) for patterns matching passwords, secrets, or API keys in plain textAffected if Plaintext passwords, secrets, or API keys are found in configuration files within the support bundle - this confirms the vulnerability is present and sensitive data was exposed
-
Verify the installed version of supportconfigRun 'rpm -qi supportutils' to check the installed version of the supportconfig packageAffected if The installed version corresponds to SUSE Linux Enterprise 10 SP3 or 11 SP1 (exact version numbers should be compared against vendor advisory listings for these service pack releases)
The environment is affected if supportconfig utility is installed and has been executed to generate support bundles that contain plaintext credentials from configuration files, particularly on SUSE Linux Enterprise 10 SP3 or 11 SP1 systems.
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 supportconfig on production systems or manually redact sensitive credentials from any generated support bundles before sharing. Apply vendor patches when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3912 — 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-2010-3912 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