libgphoto2 through 2.5.34 Heap Out-of-Bounds Read/Write via jl2005c Thumbnail Conversion
- 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. Affected Jeilin JL2005B/C/D camera driver (camlibs/jl2005c) in libgphoto2; the driver registers for USB id 0x0979:0x0227 and its initializer runs on connect The thumbnail heap overflow path requires a libgphoto2 build with HAVE_LIBJPEG
- 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? →
- 10/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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
libgphoto2 through 2.5.34 contains a heap out-of-bounds read and write vulnerability in jl2005bcd_decompress() that allows malicious USB cameras to corrupt heap memory via oversized thumbnail processing. Attackers can supply small allocation-table values and a thumbnail header byte so in-place byte-swapping exceeds the buffer by about 30 KB, leaking heap contents in preview images.
What to do
Check whether your setup matches what the bug needs.
Affected Jeilin JL2005B/C/D camera driver (camlibs/jl2005c) in libgphoto2; the driver registers for USB id 0x0979:0x0227 and its initializer runs on connect The thumbnail heap overflow path requires a libgphoto2 build with HAVE_LIBJPEGApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
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-120452
What does this mean?
The libgphoto2 driver for Jeilin JL2005B/C/D cameras can write past the end of heap and stack buffers while converting thumbnail images. The data that drives this comes from the device, so a malicious device could trigger out-of-bounds reads and writes. The advisory does not establish instruction-pointer control or code execution.Source: github.com
Am I affected, and how do I check?
Versions through libgphoto2 2.5.34 are in the affected range. The issue needs a build compiled with HAVE_LIBJPEG and involves the camlibs/jl2005c driver, which registers for USB ID 0x0979:0x0227 and runs its initializer when such a device connects. To check a build, look for libjpeg support in the configure output or build options, and check the installed version with gphoto2 --version.Source: github.com
What should I do about it?
No fixed version is listed in the checked facts, so no upgrade target can be given. Follow the libgphoto2 project's advisory for an updated release as it becomes available.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