libgphoto2 through 2.5.34 Buffer Overflow via jl2005c Camera Driver
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects the Jeilin JL2005B/C/D camera driver (camlibs/jl2005c) in libgphoto2 v2.5.34 and earlier releases carrying it. The overflow occurs when the device reports an entry count of 1022 or more. The thumbnail out-of-bounds path requires a HAVE_LIBJPEG build.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
libgphoto2 through 2.5.34 contains stack-based and heap-based buffer overflow vulnerabilities in jl2005c_init() that allow malicious USB devices to corrupt memory by supplying an unbounded allocation table entry count. Attackers can connect a spoofed Jeilin JL2005B/C/D camera reporting 1022 or more entries to overwrite the saved return address and heap data, potentially achieving code execution.
What to do
Check whether your setup matches what the bug needs.
Affects the Jeilin JL2005B/C/D camera driver (camlibs/jl2005c) in libgphoto2 v2.5.34 and earlier releases carrying it. The overflow occurs when the device reports an entry count of 1022 or more. The thumbnail out-of-bounds path requires a HAVE_LIBJPEG build.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gPhoto libgphoto2
through 2.5.34
Evidence 6
- Patch
- Patch
- Report
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120451
What does this mean?
A malicious USB camera can send an entry count of 1022 or more to the Jeilin JL2005B/C/D driver, which writes past the end of a buffer on the stack and on the heap. The facts do not establish that this leads to code execution.Source: github.com
Am I affected, and how do I check?
libgphoto2 version 2.5.34 and earlier releases that include the camlibs/jl2005c driver are affected, and the thumbnail out-of-bounds path only applies to builds using HAVE_LIBJPEG. To check, look at the libgphoto2 version reported by gphoto2 --version and whether the build was compiled with libjpeg support.Source: github.com
What should I do about it?
No fixed release is listed in the checked facts, so no upgrade target can be named from them. Check the libgphoto2 project for a newer release that includes a fix for the jl2005c driver.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data