Security readout for executives and security teams
Plain-English summary
IBM Watson CP4D Data Stores 4.6.0 can be forced into a denial-of-service condition because it lacks proper resource limits or throttling. The impact is availability, not data theft or tampering. Exploitation requires system-specific information, which lowers immediacy but still matters for exposed or mission-critical deployments.
Executive priority
Treat as a moderate availability risk. Prioritize if CP4D Data Stores supports business-critical analytics, is reachable from broad networks, or lacks operational monitoring.
Technical view
CVE-2023-27540 is a CWE-770 uncontrolled resource allocation issue in IBM Watson CP4D Data Stores 4.6.0. CVSS 3.1 is 5.9 with network attack vector, high complexity, no privileges, no user interaction, unchanged scope, and high availability impact only.
Likely exposure
Exposure is limited to organizations running IBM Watson CP4D Data Stores 4.6.0. The source bundle identifies other versions as unaffected by default, but local asset validation is required.
Exploitation context
No provided source states active exploitation, and the bundle marks KEV as false. A remote attacker would need information specific to the target system, making opportunistic exploitation less likely but not impossible.
Researcher notes
The key uncertainty is remediation detail: the supplied bundle names the affected version but does not provide a fixed version or specific workaround. Avoid claiming exploitability beyond the CVSS vector and IBM description.
Mitigation direction
- Identify any IBM Watson CP4D Data Stores 4.6.0 deployments.
- Review IBM advisory and apply any IBM-provided fix or maintenance.
- Limit network reachability to trusted administration and application paths.
- Monitor resource exhaustion, service restarts, and availability degradation.
- Escalate unresolved exposure for vendor-supported remediation guidance.
Validation and detection
- Confirm deployed CP4D Data Stores versions from asset inventory.
- Check IBM advisory and X-Force entry for current remediation guidance.
- Verify external and internal network paths to affected services.
- Review logs and monitoring for resource exhaustion or service disruption.
- Document whether compensating controls reduce unauthenticated remote reachability.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-27540 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/7009883CVE reference · vendor-advisory
- https://exchange.xforce.ibmcloud.com/vulnerabilities/248924CVE reference · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.