ReportLab vulnerable to remote code execution via paraparser
paraparser in ReportLab before 3.5.31 allows remote code execution because start_unichar in paraparser.py evaluates untrusted user input in a unichar element in a crafted XML document with '<unichar code="' followed by arbitrary Python code, a similar issue to CVE-2019-17626.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-19450US | critical9.8 | — | ||
paraparser in ReportLab before 3.5.31 allows remote code execution because start_unichar in paraparser.py evaluates untrusted user input in a unichar element in a crafted XML docum… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/MrBitBucket/reportlab-mirror/blob/master/CHANGES.mdWEB
- https://github.com/MrBitBucket/reportlab-mirror/blob/master/CHANGES.md#release-353115102019WEB
- https://github.com/advisories/GHSA-pj98-2xf6-cff5ADVISORY
- https://hg.reportlab.com/hg-public/reportlabPACKAGE
- https://lists.debian.org/debian-lts-announce/2023/09/msg00037.htmlWEB
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CHMCB2GJQKFMGVO5RWHN222NQL5XYPHZWEB
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HADPTB3SBU7IVRMDK7OL6WSQRU5AFWDZWEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-19450ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan