CVE-2013-1337
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 · uneditedMicrosoft .NET Framework 4.5 does not properly create policy requirements for custom Windows Communication Foundation (WCF) endpoint authentication in certain situations involving passwords over HTTPS, which allows remote attackers to bypass authentication by sending queries to an endpoint, aka "Authentication Bypass Vulnerability."
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 confidenceMicrosoft .NET Framework 4.5 fails to properly create policy requirements for custom Windows Communication Foundation (WCF) endpoint authentication when passwords over HTTPS are used. This allows remote attackers to bypass authentication by sending specially crafted queries to affected WCF endpoints.
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= 4.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Confirm .NET Framework 4.5 is installedCheck the installed .NET Framework version via Registry: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release value should be 378389 for .NET 4.5, or use 'gci "$env:windir\Microsoft.NET\Framework\v4.0.30319' -Recurse | % { $_.VersionInfo }' in PowerShellAffected if The installed version is exactly .NET Framework 4.5 (release key 378389)
-
Identify WCF endpoint configurationsSearch for .config files (app.config, web.config) containing <system.serviceModel> sections, or enumerate WCF services via PowerShell: 'Get-Service | Where-Object {$_.DisplayName -match "WCF"}'Affected if WCF services are hosted and their configuration files exist in the environment
-
Check for custom WCF bindings with password authenticationInspect WCF .config files for <customBinding> or <wsHttpBinding> elements containing <security mode="TransportWithMessageCredential"> or <security mode="Message"> with <message clientCredentialType="UserName"Affected if WCF endpoints are configured with custom bindings using UserName client credential type over Transport security
-
Verify HTTPS transport is enabled for affected endpointsReview the <binding> configuration to confirm security mode includes Transport (e.g., TransportWithMessageCredential or Transport), and check the <httpsTransport> or related transport element is configuredAffected if WCF endpoints with UserName credentials are configured to use HTTPS transport (not Message-only security)
The environment is affected if .NET Framework 4.5 is installed AND WCF endpoints are configured with custom UserName/password authentication over HTTPS transport.
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 dataApply the Microsoft security update for .NET Framework 4.5 (MS13-052) and audit WCF endpoint configurations to ensure custom authentication bindings are properly enforcing policy requirements.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1337 — 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-1337 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