CVE-2023-5868
Postgresql 11.0 – 11.22
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2023-5868 is a medium-severity Function Call With Incorrect Argument Type (CWE-686) vulnerability in Postgresql Postgresql. Its CVSS base score is 4.3 (Medium).
Operationally, ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-58142
Vulnerability Data
A memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with 'unknown'-type arguments. Handling 'unknown'-type values from string literals without type designation can disclose bytes, potentially revealing notable…
more
and confidential information. This issue exists due to excessive data output in aggregate function calls, enabling remote users to read some portion of system memory.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices (static analysis, code review, typed APIs, testing) directly prevent incorrect-argument calls while this single weakness addresses only a narrow slice of the control's broader intent.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect type-related defects through unit, integration, and static-analysis testing.
Secure development life cycle includes coding standards and reviews that can catch type-mismatch errors.
Application security requirements can mandate strong typing and interface contracts that prevent incorrect argument types.
Secure system architecture and engineering principles promote type-safe designs and interface definitions.
Secure coding directly addresses type safety, static analysis, and compiler warnings for argument mismatches.