Debian LinuxOperating system · Debian
CVE-2012-6071
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 · uneditednuSOAP before 0.7.3-5 does not properly check the hostname of a cert.
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 confidencenuSOAP before version 0.7.3-5 fails to properly validate SSL/TLS certificate hostnames, allowing an attacker to present a valid certificate for a different hostname and perform man-in-the-middle attacks.
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
Debian LinuxOperating system
= 8.0= 9.0= 10.0< 0.7.3-5CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 nuSOAP library versionLocate the nuSOAP library files in your application (commonly nusoap.php or lib/nusoap.php) and check the version defined in the file header or $nusoap_version variableAffected if The version is lower than 0.7.3-5 or the version cannot be determined (likely vulnerable)
-
Check Debian package version if using system packageRun 'dpkg -l | grep nusoap' or 'apt-cache policy libnusoapphp' to check if nuSOAP is installed as a Debian package and its versionAffected if The installed package version is lower than 0.7.3-5
-
Identify SSL/TLS client connections in codeSearch your codebase for nuSOAP soapclient or nusoap_http_transport instances using HTTPS URLs (grep for 'https://' in combination with nuSOAP calls)Affected if Your code makes HTTPS connections using nuSOAP without custom certificate validation (the vulnerability only applies here)
-
Check for custom certificate validation implementationSearch your codebase for stream_socket_enable_crypto calls or custom hostname verification logic within your nuSOAP integration codeAffected if No custom hostname verification is implemented and nuSOAP version is below 0.7.3-5 (vulnerable to MITM attacks)
You are affected if nuSOAP version is below 0.7.3-5 AND your application uses nuSOAP to make HTTPS/SSL connections without additional hostname verification logic.
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 data0.7.3-5
Upgrade nuSOAP to version 0.7.3-5 or later which includes proper hostname verification, or implement custom certificate validation using PHP's stream_socket_enable_crypto() with proper hostname checking.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6071 — 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-6071 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