MobilityDB version 1.3.0 and earlier contains an out-of-bounds read vulnerability in the MEOS binary and library WKB deserialization logic that allows unprivileged database users to crash the PostgreSQL backend process by supplying a crafted WKB payload with a negative length field. The negative length value wraps to a large unsigned size_t due to missing signed validation, bypasses an overflow-unsafe pointer arithmetic bounds check in wkb_parse_state_check(), and causes memcpy() in text_from_wkb_state() to operate with a corrupted unbounded length, resulting in a remote denial-of-service condition affecting all sessions on the PostgreSQL instance.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
High
Complete denial of service
CVSS Vector v4.0
Weakness Type (CWE)
References 4
https://github.com/MobilityDB/MobilityDB/releases/tag/v1.2.2
disclosure@vulncheck.com
https://github.com/MobilityDB/MobilityDB/releases/tag/v1.3.1
disclosure@vulncheck.com
https://github.com/MobilityDB/MobilityDB/security/advisories/GHSA-2c92-2w7c-pm3g
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/mobilitydb-through-out-of-bounds-read-dos-…
disclosure@vulncheck.com