dbcve.org
XmppApplication · Mellium

CVE-2022-24968

MEDIUM · 5.9 CVSS v3.1 Published 2022-02-11
Fix available
A fix is available. Upgrade to 0.21.1 or later.
See remediation →
68/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
In Mellium mellium.im/xmpp through 0.21.0, an attacker capable of spoofing DNS TXT records can redirect a WebSocket connection request to a server under their control without causing TLS certificate verification to fail. This occurs because the wrong host name is selected during this verification.

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 confidence

The mellium.im/xmpp library up to version 0.21.0 contains a hostname verification flaw in WebSocket connection handling. When a DNS TXT record is spoofed to redirect a connection to an attacker-controlled server, the TLS certificate verification incorrectly validates against the wrong hostname, allowing the connection to succeed despite the man-in-the-middle position.

MitigationUpgrade to mellium.im/xmpp version 0.21.1 or later which corrects the hostname selection during TLS verification. Additionally, enable DNSSEC on DNS resolvers to help prevent TXT record spoofing 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
XmppApplication
Affected:>= 0.18.0, < 0.21.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/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 checks

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

  1. Identify mellium.im/xmpp library usage
    Search your project dependencies (go.mod, vendor directory, or dependency lock file) for the mellium.im/xmpp import
    Affected if The library is present in dependencies
  2. Determine installed version
    Check the version of mellium.im/xmpp in your dependency manifest (go.mod file or go list -m all output)
    Affected if Version is 0.18.0 through 0.21.0 (inclusive)
  3. Verify WebSocket connection usage
    Inspect your codebase for WebSocket connection initialization using the xmpp library (look for websocket.Dial or similar WebSocket client calls)
    Affected if WebSocket connections are established using the mellium.im/xmpp library
  4. Confirm TLS certificate verification
    Review the TLS configuration in your WebSocket connection code to confirm certificate verification is enabled (check for tls.Config and VerifyServerCertificate or similar settings)
    Affected if TLS verification is active during WebSocket connections to XMPP servers
  5. Check for DNS TXT record handling
    Examine if your application performs DNS SRV or TXT lookups for XMPP server discovery
    Affected if Your application resolves XMPP servers via DNS and connects via WebSocket

Your environment is affected if mellium.im/xmpp version 0.18.0 through 0.21.0 is in use and your application establishes WebSocket connections to XMPP servers where TLS hostname verification occurs against the wrong certificate subject.

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.

dbcve · scoped
Upgrade available Upgrade to 0.21.1 or later
Fixed in 0.21.1
Interim mitigation

Upgrade to mellium.im/xmpp version 0.21.1 or later which corrects the hostname selection during TLS verification. Additionally, enable DNSSEC on DNS resolvers to help prevent TXT record spoofing attacks.

Recommended fix High confidence

0.21.1

  1. Locate the mellium.im/xmpp dependency in your project's go.mod file
  2. Update the dependency version to 0.21.1 or later (e.g., go get mellium.im/[email protected])
  3. Run 'go mod tidy' to update go.mod and go.sum files
  4. Rebuild your application to include the fixed library version
  5. Test the application to verify XMPP/WebSocket functionality works correctly with the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xmpp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24968 — 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-2022-24968 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