dbcve.org
Rocket.chatApplication

CVE-2024-39713

HIGH · 8.6 CVSS v3.1 Published 2024-08-05
Fix available
A fix is available. Upgrade to 6.10.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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
A Server-Side Request Forgery (SSRF) affects Rocket.Chat's Twilio webhook endpoint before version 6.10.1.

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

A Server-Side Request Forgery (SSRF) vulnerability exists in Rocket.Chat's Twilio webhook endpoint before version 6.10.1. This allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or bypassing network restrictions.

MitigationUpgrade Rocket.Chat to version 6.10.1 or later. Additionally, implement network segmentation and restrict outbound connections to minimize the impact of SSRF exploitation.

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
Rocket.chatApplication
Affected:< 6.10.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
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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. Check Rocket.Chat version
    Access the Rocket.Chat admin panel (usually at /admin/info) or use the API endpoint /api/info to retrieve the server version number
    Affected if The displayed version is lower than 6.10.1 (e.g., 6.10.0, 6.9.x, or earlier)
  2. Verify Twilio integration status
    Navigate to the Rocket.Chat admin panel under Integrations or Webhooks section, and check if a Twilio webhook or integration is enabled/configured
    Affected if A Twilio webhook or integration is active in the system
  3. Confirm webhook endpoint is accessible
    Attempt to access the Twilio webhook endpoint path (typically /webhook/twilio or similar) via the Rocket.Chat server to verify the endpoint exists and responds
    Affected if The endpoint responds and accepts requests, indicating the vulnerable feature is exposed
  4. Review outgoing network restrictions
    Inspect Rocket.Chat server firewall rules, security groups, or network policies to determine if outbound HTTP requests from the server are unrestricted
    Affected if The server has broad outbound access allowing arbitrary HTTP requests to internal or external destinations

You are affected if your Rocket.Chat version is below 6.10.1 AND the Twilio webhook integration is enabled, as this combination exposes the SSRF vulnerability.

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 6.10.1 or later
Fixed in 6.10.1
Interim mitigation

Upgrade Rocket.Chat to version 6.10.1 or later. Additionally, implement network segmentation and restrict outbound connections to minimize the impact of SSRF exploitation.

Recommended fix Moderate confidence

Rocket.Chat 6.10.1

  1. Identify your current Rocket.Chat installation method (Docker, snap, npm, or other)
  2. Review the Rocket.Chat 6.10.1 release notes for your installation method
  3. Create a backup of your current Rocket.Chat database and configuration
  4. For Docker installations: Stop the container, pull the new image (rocketchat/rocket.chat:6.10.1), and restart
  5. For non-Docker installations: Follow the official upgrade documentation for your method
  6. Verify the upgrade was successful by checking the Rocket.Chat version
  7. Test the Twilio webhook functionality to confirm it works correctly
Caveat Review the 6.10.1 release notes for any breaking changes specific to your configuration before upgrading

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

Fix this in Rocket.chat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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