dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-31714

HIGH · 7.5 CVSS v3.1 Published 2024-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Buffer Overflow vulnerability in Waxlab wax v.0.9-3 and before allows an attacker to cause a denial of service via the Lua library component.

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 buffer overflow vulnerability exists in the Lua library component of Waxlab wax version 0.9-3 and earlier versions. The overflow can be triggered by an attacker, leading to denial of service.

MitigationUpdate Waxlab wax to a version beyond 0.9-3 once a patched release is available. Implement input validation and bounds checking in Lua library interactions as an interim measure.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Verify Waxlab wax is installed
    Search for the wax binary or package on the system using commands like 'which wax', 'dpkg -l | grep wax', 'rpm -qa | grep wax', or by listing files in common installation directories
    Affected if Waxlab wax is not found on the system (not affected)
  2. Determine the installed version of Waxlab wax
    Run 'wax --version' or 'wax -v' if available, or query the package manager (dpkg -l wax, rpm -qi wax) to retrieve the installed version number
    Affected if Version cannot be determined or shows 0.9-3 or earlier
  3. Compare version against affected range
    If a version number is obtained, compare it to 0.9-3. Any version equal to or lower than 0.9-3 falls within the affected range (for example: 0.9-3, 0.9-2, 0.9, 0.8, 0.7)
    Affected if Version is 0.9-3 or any earlier version in the 0.x series
  4. Confirm Lua library component is in use
    Check Waxlab wax configuration files, runtime settings, or documentation to determine whether the Lua library component is enabled, loaded, or actively processing Lua scripts
    Affected if Lua library is enabled or being used by the wax installation

A system is affected if Waxlab wax version 0.9-3 or earlier is installed AND the Lua library component is enabled or in use, as the buffer overflow exists specifically in the Lua library portion of wax.

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

Update Waxlab wax to a version beyond 0.9-3 once a patched release is available. Implement input validation and bounds checking in Lua library interactions as an interim measure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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