CVE-2023-27291
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Watson CP4D Data Stores 4.6.0, 4.6.1, 4.6.2, and 4.6.3 does not encrypt sensitive or critical information before storage or transmission which could allow an attacker to obtain sensitive information. IBM X-Force ID: 248740.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM Watson CP4D Data Stores versions 4.6.0 through 4.6.3 fail to encrypt sensitive or critical information before storage or transmission, potentially exposing confidential data to unauthorized attackers who gain access to stored data or network traffic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.6.0= 4.6.1= 4.6.2= 4.6.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Watson CP4D Data Stores versionLocate the version information for the IBM Watson CP4D Data Stores installation, typically found in the product UI under 'About' or 'System Information', or via the administration CLI if availableAffected if The installed version is 4.6.0, 4.6.1, 4.6.2, or 4.6.3
-
Verify data-at-rest encryption configurationAccess the IBM Watson CP4D Data Stores administrative console or configuration files and locate the encryption settings for stored data. Check whether encryption for data at rest is enabled or set to 'disabled'Affected if Encryption for data at rest is disabled or not configured in the Data Stores settings
-
Verify data-in-transit encryption configurationAccess the IBM Watson CP4D Data Stores administrative console or configuration files and locate the TLS/SSL or encryption settings for network communications. Check whether encryption for data in transit is enabled or set to 'disabled'Affected if Encryption for data in transit (TLS/SSL) is disabled or not configured in the Data Stores settings
-
Review storage subsystem encryption statusInspect the underlying storage configuration used by Data Stores (such as database encryption settings, filesystem encryption, or storage class configuration) to determine if encryption is applied at the storage layerAffected if No encryption is enabled at the storage subsystem level and the product version is within the affected range
If the installed version is 4.6.0 through 4.6.3 and encryption for data at rest or in transit is not enabled in the configuration, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnable encryption for data at rest and in transit within the IBM Watson CP4D Data Stores configuration, or contact IBM for available patches/updates that address this encryption deficiency.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27291 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-27291 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data