dbcve.org
CWE-93Weakness · CWE-93

CVE-2024-51981

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An unauthenticated attacker may perform a blind server side request forgery (SSRF), due to a CLRF injection issue that can be leveraged to perform HTTP request smuggling. This SSRF leverages the WS-Addressing feature used during a WS-Eventing subscription SOAP operation. The attacker can control all the HTTP data sent in the SSRF connection, but the attacker can not receive any data back from this connection.

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 · moderate confidence

A blind SSRF vulnerability exists in the WS-Eventing subscription feature due to a CRLF injection flaw. An unauthenticated attacker can inject HTTP headers via WS-Addressing in SOAP requests, enabling HTTP request smuggling to trigger outbound connections to attacker-controlled servers. The attacker controls all request data but cannot receive responses (blind).

MitigationDisable or restrict WS-Eventing functionality if not required; implement strict input validation on SOAP headers; consider WAF rules to block CRLF injection patterns in WS-Addressing headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify WS-Eventing endpoint exposure
    Review web server configuration files (web.config, applicationHost.config for IIS; service web.config for WCF) for <wsEventing> or similar WS-Eventing handler registrations, and check if SOAP/WS-Eventing endpoints are mapped in IIS or the application's WSDL definitions
    Affected if WS-Eventing is enabled and a public-facing SOAP endpoint exists that processes WS-Addressing headers
  2. Confirm WS-Addressing header processing
    Examine the application's SOAP message handlers or WCF behaviors configured to process wsA:Action, wsA:To, and other WS-Addresssing elements within the WS-Eventing subscription workflow
    Affected if The application processes WS-Addressing headers in SOAP requests without strict validation on CRLF characters
  3. Check for CRLF injection filtering
    Review any custom SOAP filters, message inspectors, or input validation code that handles WS-Addressing headers; search for string replacement or validation logic targeting newline characters (\r, \n, %0D, %0A)
    Affected if No input validation or filtering is applied to WS-Addressing header values before they are used in HTTP requests
  4. Review WS-Eventing subscription configuration
    Inspect the subscription manager or event sink configuration to determine if subscriber-supplied endpoint URLs are used to establish outbound HTTP connections
    Affected if The WS-Eventing subscription feature allows subscribers to specify callback URLs that the server will connect to without sufficient validation
  5. Audit access controls on WS-Eventing
    Check authentication and authorization settings on WS-Eventing endpoints; verify whether anonymous or unauthenticated requests can reach the subscription creation interface
    Affected if WS-Eventing subscription endpoints are accessible without authentication

You are affected if WS-Eventing is enabled and accessible without strict input validation on WS-Addressing headers, allowing an unauthenticated attacker to inject CRLF sequences and trigger blind outbound HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or restrict WS-Eventing functionality if not required; implement strict input validation on SOAP headers; consider WAF rules to block CRLF injection patterns in WS-Addressing headers.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,104.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51981 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51981 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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