GHSA-rgqc-3x5p-6gwg: Input Validation
A malicious or compromised server can return a binary hstore value with an invalid internal length field, causing the client to panic while decoding it.
Applications that connect only to a trusted database are not exposed; the risk applies to clients that may connect to untrusted or user-supplied servers, or whose connection can be intercepted by a man-in-the-middle.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rust/postgres-protocolto a version that resolves this vulnerability.Fixed in 0.6.12
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Clients are exposed when they may connect to untrusted or user-supplied database servers, or when a man-in-the-middle can intercept the connection. Applications that connect only to a trusted database are not exposed.
What does an attacker need to do to trigger the failure?
An attacker controlling or compromising the server, or positioned to modify the connection as a man-in-the-middle, must return a binary hstore value with an invalid internal length field. Decoding that value causes the client to panic.
What is the impact of successful exploitation?
The affected client panics while decoding the malformed binary hstore value. The provided information describes a denial-of-service condition in the client.