CVE-2025-2327
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 · uneditedA flaw exists in FlashArray whereby the Key Encryption Key (KEK) is logged during key rotation when RDL is configured.
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 confidenceFlashArray stores Key Encryption Keys (KEKs) used to protect data at rest. During key rotation operations when RDL (likely Replication Data Log) is configured, the KEK is being written to system logs, exposing sensitive cryptographic material. An attacker with log access could recover the KEK and decrypt protected data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Confirm FlashArray productIdentify the storage system as Pure Storage FlashArray. Check the product model or management interface for 'FlashArray' or 'Pure Storage' branding.Affected if The product is not a Pure Storage FlashArray system.
-
Verify RDL configuration statusCheck whether Replication Data Log (RDL) is enabled on the FlashArray. This can typically be found in the array management settings, replication configuration, or by running the Pure Storage CLI command 'purevol list --replication' or checking the replication log configuration.Affected if RDL is not configured on the FlashArray.
-
Locate system logs during key rotationAccess the FlashArray system logs. These are typically found in the management UI under 'Logs' or via CLI commands. Focus on logs generated during or after key rotation operations, which are often scheduled or triggered manually.Affected if No access to system logs is available.
-
Search for KEK patterns in logsExamine the system logs for plaintext or hexadecimal strings resembling cryptographic key material. Look for patterns that appear during key rotation events, such as long hexadecimal strings, base64-encoded data, or explicit mentions of 'KEK', 'Key Encryption Key', or 'key' in proximity to rotation timestamps.Affected if The logs contain strings that match Key Encryption Key (KEK) format during key rotation operations when RDL is configured.
If RDL is configured on a Pure Storage FlashArray and the system logs contain Key Encryption Key material during or after key rotation operations, 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 dataDisable or reconfigure logging to prevent KEK from being written to logs during key rotation, or apply vendor patch to remove KEK from log output.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2327 — 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-2025-2327 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