Heap-based Buffer OverflowWeakness · CWE-122

CVE-2024-46461

HIGH · 8.0 CVSS v3.1 Published 2024-09-25
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

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
VLC media player 3.0.20 and earlier is vulnerable to denial of service through an integer overflow which could be triggered with a maliciously crafted mms stream (heap based overflow). If successful, a malicious third party could trigger either a crash of VLC or an arbitrary code execution with the target user's privileges.

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

VLC media player 3.0.20 and earlier contains an integer overflow vulnerability in MMS stream parsing. When processing a maliciously crafted MMS stream, the integer overflow leads to heap-based buffer overflow, potentially allowing crash (DoS) or arbitrary code execution with the user's privileges.

MitigationUpdate VLC media player to a version newer than 3.0.20. Avoid opening untrusted MMS streams from unknown sources until the update is applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 VLC media player is installed
    Locate the VLC executable on the system. On Windows, check common installation paths like C:\Program Files\VideoLAN\VLC\vlc.exe. On Linux, run 'which vlc' or check /usr/bin/vlc. On macOS, check /Applications/VLC.app.
    Affected if VLC is not found on the system, then this CVE does not apply.
  2. Determine the installed VLC version
    Run 'vlc --version' from the command line, or right-click the vlc.exe file and view Properties > Details to see the File Version. On Linux, also try 'vlc -version'.
    Affected if The version displayed is 3.0.20 or any earlier version (such as 3.0.19, 3.0.18, etc.).
  3. Compare the version to the affected range
    Review the version number obtained. The CVE states that versions 3.0.20 and earlier are affected. Versions newer than 3.0.20 (such as 3.0.21 and later) are not affected.
    Affected if The installed version is 3.0.20 or earlier.
  4. Check if MMS streaming functionality is accessible
    In VLC, go to Media > Open Network Stream (or press Ctrl+N). Look for MMS:// or MMSH:// protocol options in the network stream dialog.
    Affected if MMS protocol input fields are available and the user can enter MMS stream URLs.

The system is affected if VLC media player version 3.0.20 or earlier is installed and the MMS streaming feature is accessible for processing network streams.

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

Update VLC media player to a version newer than 3.0.20. Avoid opening untrusted MMS streams from unknown sources until the update is applied.

Recommended fix High confidence

VLC media player 3.0.21 (or later in the 3.0.x branch)

  1. 1. Open VLC media player and go to 'Help' > 'Check for Updates' to see if version 3.0.21 or later is available for your platform.
  2. 2. Alternatively, download the latest VLC 3.0.x release (3.0.21 or later) from the official VideoLAN website: https://www.videolan.org/vlc/
  3. 3. Install the new version, ensuring you close any running VLC instances before installation.
  4. 4. After upgrading, verify the new version by opening VLC and checking 'Help' > 'About VLC media player' shows version 3.0.21 or newer.
Caveat Minimal risk - patch release within same major version branch; standard upgrade procedure

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-46461 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