Cyber Resilience

CVE-2023-28512

Ibm Watson Cp4D Data Stores 4.6.0 … 4.6.2

Published
03 March 2024
Modified
29 January 2025
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0055 43th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-28512 is a medium-severity External Control of Assumed-Immutable Web Parameter (CWE-472) vulnerability in Ibm Watson Cp4D Data Stores. Its CVSS base score is 5.9 (Medium).

Operationally, ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Watson CP4D Data Stores 4.6.0, 4.6.1, and 4.6.2 could allow an attacker with specific knowledge about the system to manipulate data due to improper input validation. IBM X-Force ID: 250396.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-27291Same product: Ibm Watson Cp4D Data Stores
CVE-2023-26282Same product: Ibm Watson Cp4D Data Stores
CVE-2023-40694Same product: Ibm Watson Cp4D Data Stores
CVE-2020-4430Same vendor: Ibm
CVE-2025-27903Same vendor: Ibm
CVE-2024-49818Same vendor: Ibm
CVE-2023-47718Same vendor: Ibm
CVE-2024-49792Same vendor: Ibm
CVE-2025-36185Same vendor: Ibm
CVE-2024-39732Same vendor: Ibm

Affected Assets

ibm
watson cp4d data stores
4.6.0, 4.6.1, 4.6.2

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require server-side validation of all inputs instead of trusting client-supplied immutable parameters.

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.

prevents

Secure coding standards require server-side verification of client-supplied data, eliminating the root cause of external control of immutable parameters.

detects

Security testing in development and acceptance will detect parameter tampering vulnerabilities before deployment.

prevents

Secure development lifecycle mandates input validation and integrity checks that directly prevent external tampering of assumed-immutable parameters.

prevents

Application security requirements explicitly call for validation of all inputs, including hidden fields, mitigating CWE-472.

none

Information access restriction can limit which parameters users may influence, providing a secondary layer of defense.

References