First published: Tue Jan 14 2025(Updated: )
Important: raptor2 security update
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/raptor2 | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2 | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-debuginfo | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-debuginfo | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-debugsource | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-debugsource | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2 | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-debuginfo | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-debugsource | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2 | <2.0.15-32.el9_5.aa | 2.0.15-32.el9_5.aa |
redhat/raptor2-debuginfo | <2.0.15-32.el9_5.aa | 2.0.15-32.el9_5.aa |
redhat/raptor2-debugsource | <2.0.15-32.el9_5.aa | 2.0.15-32.el9_5.aa |
redhat/raptor2-devel | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-devel | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-devel | <2.0.15-32.el9_5 | 2.0.15-32.el9_5 |
redhat/raptor2-devel | <2.0.15-32.el9_5.aa | 2.0.15-32.el9_5.aa |
Red Hat CodeReady Linux Builder for x86_64 - Extended Update Support | ||
Red Hat Enterprise Linux 8 | ||
Red Hat Enterprise Linux Server for IBM z Systems | ||
Red Hat Enterprise Linux for ARM 64 | ||
Red Hat CodeReady Linux Builder for x86_64 - Extended Update Support | ||
Red Hat Enterprise Linux for Power, little endian - Extended Update Support | ||
Red Hat CodeReady Linux Builder for IBM z Systems | ||
Red Hat CodeReady Linux Builder for ARM 64 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2025:0312 is classified as important.
To fix RHSA-2025:0312, update raptor2 to version 2.0.15-32.el9_5.
RHSA-2025:0312 addresses an integer underflow vulnerability when normalizing a URI using the turtle parser.
RHSA-2025:0312 affects multiple packages including raptor2, raptor2-debuginfo, and raptor2-devel.
There are no official workarounds provided for RHSA-2025:0312; applying the security update is recommended.