Description
The address_standardizer extension for PostGIS through 3.7.0, fixed in commit 423570b, contains an out-of-bounds write vulnerability that allows a database user with the ability to supply caller-controlled relation names to standardize_address() to trigger memory corruption by providing a rules table with a classification Type value exceeding the fixed class range. Attackers can craft a malicious rules table entry with an oversized rule type value that is used without bounds checking as an index into an internal output-link table, resulting in an out-of-bounds write.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
PostGIS address_standardizer
Default version status: affected
0 to < 423570b0dbf6cd9f6fc36de28a636e7b6e9aa8aaaffected
pkg:github/postgis/address_standardizerReferences
- https://mehmetince.net/part-1-6-systemic-risks-in-the-managed-postgresql-industry-extension-risks-are-real-exploiting-postgis-memory-corruption-bug-at-neondb-supabase-and-many-more/ ↗
- https://github.com/postgis/address_standardizer/pull/3 ↗
- https://github.com/postgis/address_standardizer/pull/4 ↗
- https://github.com/postgis/address_standardizer/commit/423570b0dbf6cd9f6fc36de28a636e7b6e9aa8aa ↗
- https://www.vulncheck.com/advisories/postgis-address-standardizer-out-of-bounds-write-via-standardize-address ↗