dbcve.org
MongooseApplication · Cesanta

CVE-2024-42387

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to after 7.14 or later.
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
Use of Out-of-range Pointer Offset vulnerability in Cesanta Mongoose Web Server v7.14 allows an attacker to send an unexpected TLS packet and force the application to read unintended heap memory space.

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

Out-of-bounds read vulnerability in Mongoose Web Server v7.14 TLS handling. An attacker can send malformed TLS packets to trigger the server to read heap memory outside intended boundaries, potentially leaking sensitive heap data.

MitigationUpdate to a patched version of Mongoose Web Server. If immediate patching is not feasible, implement network-level filtering to block unexpected TLS packets and monitor for anomalous TLS handshake patterns.

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
MongooseApplication
Affected:<= 7.14

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 Mongoose version
    Run 'mongoose --version' or check the binary/library metadata to determine the installed version number
    Affected if version is 7.14 or lower (any version <= 7.14)
  2. Confirm TLS support is active
    Review the Mongoose configuration file or startup parameters to verify TLS/HTTPS is enabled. Look for TLS-related settings such as 'ssl' or 'tls' flags, or SSL certificate configuration directives
    Affected if TLS/HTTPS support is enabled - the vulnerability only triggers when the server is handling TLS connections
  3. Assess network exposure
    Check if the Mongoose server is bound to a network interface that accepts external TLS connections. Review firewall rules and access controls around the Mongoose service
    Affected if the TLS endpoint is reachable from untrusted networks, increasing the likelihood of receiving malformed TLS packets

A user is affected if they are running Mongoose version 7.14 or earlier with TLS/HTTPS support enabled and accessible to network traffic.

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
Upgrade available Upgrade to a release after 7.14
Interim mitigation

Update to a patched version of Mongoose Web Server. If immediate patching is not feasible, implement network-level filtering to block unexpected TLS packets and monitor for anomalous TLS handshake patterns.

Fix this in Mongoose Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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