Bug 2554367 - CVE-2026-111458 ssldump: ssldump: Arbitrary code execution via heap-based buffer overflow in certificate fingerprint formatting [fedora-all]
Summary: CVE-2026-111458 ssldump: ssldump: Arbitrary code execution via heap-based buf...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: ssldump
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["a5ddc8a4-b124-4d36-bf00-6...
Depends On:
Blocks: CVE-2026-111458
TreeView+ depends on / blocked
 
Reported: 2026-10-16 18:38 UTC by Vladimir Vasilev
Modified: 2026-10-16 18:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-10-16 18:38:00 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The fanx_fingerprint function in ssl/sslxprint.c of ssldump allocates a heap buffer for formatting FAN/1 X.509 certificate fingerprints. The allocation size is computed as strlen(b64) + strlen(hex) + 31, but the format string "fan1:x509:server:passive:%s:sha256:%s" contains 33 fixed characters in addition to the two variable-length fields and a null terminator, requiring strlen(b64) + strlen(hex) + 34 bytes. This miscalculation results in a 3-byte heap-based buffer overflow on every invocation of the function with valid inputs. The overflow occurs because sprintf writes the full formatted string into the undersized heap buffer without bounds checking. An attacker who can supply a crafted pcap file containing a TLS X.509 certificate to a user running ssldump with FAN/1 fingerprinting enabled (for example with the -j -N options) can trigger the overflow. The resulting heap corruption may lead to denial of service through a crash or, in a worst-case scenario, arbitrary code execution in the context of the user running ssldump. The vulnerability is deterministic and requires no special privileges beyond the ability to provide input to the tool.


Note You need to log in before you can comment on or make changes to this bug.