Application crash via malformed Nikon EXIF data
Published Jan 11, 2024 · Updated Jun 17, 2025
Heap-based buffer overflow in exiftags 1.01 allows context-dependent attackers to crash the utility via a crafted JPEG file. In nikon_prop1 in nikon.c, snprintf writes 28 bytes beyond a 21-byte heap allocation while processing malformed Nikon EXIF properties. A user must run exiftags on the attacker-supplied image; the demonstrated consequence is an AddressSanitizer-detected abort.
Summary
What happened
Heap-based buffer overflow in exiftags 1.01 allows context-dependent attackers to crash the utility via a crafted JPEG file. In nikon_prop1 in nikon.c, snprintf writes 28 bytes beyond a 21-byte heap allocation while processing malformed Nikon EXIF properties. A user must run exiftags on the attacker-supplied image; the demonstrated consequence is an AddressSanitizer-detected abort.
The record
- CVE
- CVE-2023-50671
- Published
- Jan 11, 2024
- Updated
- Jun 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- sample_exiftags.zip crash samplesproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo