-
Notifications
You must be signed in to change notification settings - Fork 37
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
AddressSanitizer: heap-buffer-overflow on IccTagXml #55
Comments
This is an interesting .icc profile and it breaks many other implementations :-) I added some code to bailout early and fail to read the file [seperate issue to be resolved] in PR #64. It is a defensive patch that will be evaded with more fuzzing. |
Hello @RootUp I will request a CVE for this issue. CVE SummaryThe AddressSanitizer report indicates a heap-buffer-overflow issue in the AnalysisCall Stack: The function Proposed FixesEnsure that the CIccMBB::NewCurvesM function allocates memory for the array of LPIccCurve pointers. Add checks in icCurvesToXml to verify that each CIccCurve pointer is properly initialized before accessing it. Error messages in the icCurvesFromXml function to provide clearer diagnostics when XML parsing fails. MetricsCVSS 3.1 Base Score: 8.8 |
Updated on 14 Sep 2024 RE: CVE Request 1699842 for CVE ID Request I have requested a status from CVE. |
Is this issue still open or has it been indirectly resolved? |
A heap based buffer overflow was identified on
IccToXml
while fuzzing the vulnerability is triggered with a crafted.icc
profile file. Attaching the same for reference.GDB:
ASAN:
sample.icc.zip
The text was updated successfully, but these errors were encountered: