First published: Thu Aug 08 2024(Updated: )
Last updated 14 November 2024
Credit: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
Affected Software | Affected Version | How to fix |
---|---|---|
debian/postgresql-13 | 13.16-0+deb11u1 13.20-0+deb11u1 | |
debian/postgresql-15 | 15.10-0+deb12u1 | |
PostgreSQL Common | >=12.0<12.20 | |
PostgreSQL Common | >=13.0<13.16 | |
PostgreSQL Common | >=14.0<14.13 | |
PostgreSQL Common | >=15.0<15.8 | |
PostgreSQL Common | >=16.0<16.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2024-7348 has not been explicitly detailed and likely varies based on the specific context of the affected systems.
To mitigate CVE-2024-7348, update PostgreSQL to a version that is not affected, namely versions later than the specified vulnerable versions.
CVE-2024-7348 affects specific versions of PostgreSQL, particularly versions 12.0 up to 12.20, 13.0 up to 13.16, and others listed in the advisory.
As of now, there are no publicly known exploits targeting CVE-2024-7348, but monitoring and patching is advised.
Currently, the recommended approach is to upgrade PostgreSQL to a secure version rather than relying on workarounds.