CVE-2022-0085: Server-Side Request Forgery in dompdf/dompdf
Published Jun 23, 2022
·Updated
Server-Side Request Forgery (SSRF) in GitHub repository dompdf/dompdf prior to 2.0.0.
Other sources
Server-Side Request Forgery in dompdf/dompdf
Affected Software
4 affected componentsFixes available
composer/dompdf/dompdf<2.0.0
composer/dompdf/dompdf<2.0.0
2.0.0
Dompdf Project Dompdf<2.0.0
composer/dompdf/dompdf<2.0.0
2.0.0
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/dompdf/dompdfto a version that resolves this vulnerability.Fixed in 2.0.0
Event History
Jun 23, 2022
Advisory Published
01:55 PM
Data Sourced
via Packagist·01:55 PM
DescriptionSeverityAffected Software
Jun 28, 2022
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 29, 2022
Advisory Published
via GitHub·12:00 AM
Data Sourced
via GitHub·12:00 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is CVE-2022-0085?
CVE-2022-0085 refers to a Server-Side Request Forgery (SSRF) vulnerability in the dompdf/dompdf GitHub repository prior to version 2.0.0.
2
How severe is CVE-2022-0085?
CVE-2022-0085 has a severity value of 5.3, which is considered medium.
3
What software is affected by CVE-2022-0085?
CVE-2022-0085 affects the dompdf/dompdf package version prior to 2.0.0.
4
How can I fix CVE-2022-0085?
To fix CVE-2022-0085, it is recommended to update the dompdf/dompdf package to version 2.0.0 or later.