Skip to content
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

URI validation failure does not halt font registration in Dompdf 2.0.0 #2994

Closed
bsweeney opened this issue Aug 25, 2022 · 0 comments · Fixed by #2995
Closed

URI validation failure does not halt font registration in Dompdf 2.0.0 #2994

bsweeney opened this issue Aug 25, 2022 · 0 comments · Fixed by #2995
Milestone

Comments

@bsweeney
Copy link
Member

bsweeney commented Aug 25, 2022

When a font is registered through the @font-face rule the URL is run through validation that was implemented to address the issues outlined in #2564. The validation logic specific to the font-face rule, however, does not actually halt processing of the font when validation fails. As a result, a system running Dompdf 2.0.0 is vulnerable to remote file inclusion though the font installation routines and that may lead to code execution due to PHAR deserialization vulnerability if the system is running a vulnerable version of PHP (< 8.0.0).

References:

@bsweeney bsweeney added the bug label Aug 25, 2022
@bsweeney bsweeney added this to the 2.0.1 milestone Aug 25, 2022
@bsweeney bsweeney changed the title URI validation failure does not halt font registration URI validation failure does not halt font registration in Dompdf 2.0.0 Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant