PostGIS address_standardizer Out-of-Bounds Write via standardize_address()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| PostGIS | address_standardizer | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Postgis | Address Standardizer |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.820% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgis
Postgis address Standardizer |
|
| Vendors & Products |
Postgis
Postgis address Standardizer |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PostGIS address_standardizer Out-of-Bounds Write via standardize_address() | |
| Weaknesses | CWE-787 | |
| References |
|
|
| Metrics |
cvssV3_1
|