FedoraOperating system · Fedoraproject
CVE-2023-51791
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 · uneditedBuffer Overflow vulenrability in Ffmpeg v.N113007-g8d24a28d06 allows a local attacker to execute arbitrary code via the libavcodec/jpegxl_parser.c in gen_alias_map.
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 confidenceA buffer overflow vulnerability exists in FFmpeg's JPEG XL parser (libavcodec/jpegxl_parser.c) within the gen_alias_map function. A local attacker can exploit this by providing a specially crafted input that overflows a buffer, potentially leading to arbitrary code execution.
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
FedoraOperating system
= 38= 39= 40= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.1= 7.1.1= 7.1.2= 7.1.3= 7.2= 8.0= 8.0.1= 8.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed FFmpeg versionRun `ffmpeg -version` and examine the version number in the outputAffected if The version is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.1, 7.1.1, 7.1.2, 7.1.3, 7.2, 8.0, 8.0.1, or 8.1 (exactly as listed in affected versions)
-
Verify JPEG XL decoder support is enabledRun `ffmpeg -codecs 2>/dev/null | grep -i jpegxl` or `ffmpeg -decoders 2>/dev/null | grep -i jpegxl`Affected if Output shows jpegxl decoder is available (the vulnerability cannot be triggered without JPEG XL support built into FFmpeg)
-
Confirm JPEG XL demuxer/formats supportRun `ffmpeg -formats 2>/dev/null | grep -i jpegxl`Affected if Output shows JPEG XL format support (demuxer or decoder) is present in the build
You are affected if you are running an affected FFmpeg version (7.0-8.1.1) with JPEG XL decoding or demuxing support enabled, and you process untrusted JPEG XL files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate FFmpeg to a version beyond v.N113007-g8d24a28d06 that includes proper bounds checking in the jpegxl_parser.c gen_alias_map function, or apply a patch that adds validation for buffer sizes before memory operations.
FFmpeg 7.1 or later stable release
- 1. Back up your current FFmpeg installation and any custom configurations.
- 2. Update your system package cache: `dnf check-update` (for Fedora)
- 3. Install the updated FFmpeg package: `dnf update ffmpeg`
- 4. Verify the new version includes the fix by checking: `ffmpeg -version`
- 5. Test with the affected JPEGXL parsing functionality to confirm the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51791 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-51791 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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