postgres-protocol: Panic decoding a malformed `hstore` value allows denial of service
Priority LOW 38CWE-20Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-248.
Summary
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.
Why it matters now
Fix Fixed postgres-protocol (crates.io): 0.6.12
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | postgres-protocol (crates.io) | before 0.6.12 | 0.6.12 | Patch available | GHSA-rgqc-3x5p-6gwg |
- postgres-protocol (crates.io) Vendor— Affected before 0.6.12 Fixed in 0.6.12 Patch available GHSA-rgqc-3x5p-6gwg
Remediation
- Fix · GHSA-rgqc-3x5p-6gwg postgres-protocol (crates.io) Fixed in 0.6.12 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-rgqc-3x5p-6gwg
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences