New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kodi image exif parse bug #22377
Comments
|
Potential fix: fritsch@367cc80 Why I say potential:
It might be better to remove kodi's code and somehow rely on upstream libraries to not run into such issues in the future. |
|
Can this be rated as a vulnerability? For example, CVE (Common Vulnerabilities and Exposure) |
|
I informed the team internally and the process now starts to run. It is definitely a potential DOS and should be handled as such. As an inactive senior member I don't really know the processes internally anymore, but I made sure the team was made aware. Thanks much for reporting. |
|
Thank you Once the process is complete, CVE will proceed with registration from the internal team that manages Kodi? |
|
Btw. do you test old exploits? I fixed now all illegal memory accesses and it seems, that you are using drafted images, that were used to fix these issues in upstream code some years ago. Is this some "university" bug hunting game? Just out of curiosity, it needs fixing - that is clear. Second part: fritsch@54df944 |
|
No, it's just that we've found an unexpected bug in the process of using, researching, and testing Kodi software on Android platforms, and we're reporting it because we want it to be officially patched. I didn't think it was a bug bounty. but I'd be happy if it was recognized as a vulnerability to illegal memory access. The process seems to have been completed because you finally told me that the patch was applied. |
|
Thanks again very much. We still need to review the issue. Let those reports coming :-). We are very short on people working on kodi, it's a freetime project you know. So whenever you find something and have an idea on how to fix it, feel free to contribute. It would also be great if you could verify that kodi with the linked PullRequest is also fine for you. I tested with the memory sanitizers on AMD64, so depending on ptr sizes / etc. there might be differences. Thanks again for your time you invested into kodi. |

Bug report
Describe the bug
After inserting the wrong/malformed image file into the USB storage device and mounting it, run kodi to run the Picture application. Exifparse crashes while scanning (reading) the wrong image files included in the USB storage device, leading to the termination of the process
Expected Behavior
If you include an invalid image file, the kodi process crashes, you can check the memory address through the internal crash log.
Actual Behavior
Possible Fix
To Reproduce
Steps to reproduce the behavior:
image.zip
Debuglog
kodi_crashlog-20230103_053835.log
kodi_crashlog-20230103_071817.log
kodi_crashlog-20230103_071903.log
Screenshots
Additional context or screenshots (if appropriate)
Here is some additional context or explanation that might help:
Your Environment
Used Operating system:
[O] Android
iOS
tvOS
[0] Linux
macOS
Windows
Windows UWP
Operating system version/name: Raspberrypi 4
Kodi version: Latest Version.
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.
The text was updated successfully, but these errors were encountered: