- Vulnerability/
- RHSA-2020:3248
RHSA-2020:3248: Important: Red Hat build of Quarkus 1.3.4 SP1 release and security update
First published: Thu Jul 30 2020(Updated: )
This release of Red Hat build of Quarkus 1.3.4 SP1 includes security updates, bug fixes, and enhancements. For more information, see the release notes page listed in the References section.<br>Security Fix(es):<br><li> postgresql-jdbc: XML external entity (XXE) vulnerability in PgSQLXML(CVE-2020-13692)</li> <li> RESTEasy: Caching routes in RootNode may result in DoS (CVE-2020-14326)</li> For more details about the security issues and their impact, the CVSS score, acknowledgments, and other related information see the CVE pages listed in the References section.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Quarkus RESTEasy |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi?id=1852985
- https://bugzilla.redhat.com/show_bug.cgi?id=1855826
- https://access.redhat.com/security/updates/classification/#important
- https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=redhat.quarkus&downloadType=distributions&version=1.3.4.SP1
- https://access.redhat.com/documentation/en-us/red_hat_build_of_quarkus/1.3/html/release_notes_for_red_hat_build_of_quarkus_1.3/index
- https://access.redhat.com/articles/4966181
- https://access.redhat.com/errata/RHSA-2020:3248 (Advisory)
Frequently Asked Questions
What is the severity of RHSA-2020:3248?
The severity of RHSA-2020:3248 is classified as important.
What vulnerabilities are addressed in RHSA-2020:3248?
RHSA-2020:3248 addresses an XML external entity (XXE) vulnerability in postgresql-jdbc.
How do I fix RHSA-2020:3248?
To fix RHSA-2020:3248, you need to update the Red Hat build of Quarkus to version 1.3.4 SP1 or later.
What is the impact of the vulnerability in RHSA-2020:3248?
The impact of the XML external entity vulnerability can lead to exposure of sensitive data or denial of service.
Is there a workaround for RHSA-2020:3248 if I cannot update immediately?
There are no specific workarounds for RHSA-2020:3248, so updating is the recommended action.
- agent/severity
- agent/type
- agent/event
- agent/last-modified-date
- collector/redhat-errata
- source/Red Hat
- anchor-id/RHSA-2020:3248
- agent/first-publish-date
- agent/trending
- agent/remedy
- agent/references
- agent/title
- agent/description
- agent/source
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/red hat
- canonical/red hat quarkus resteasy