CVE-2023-23346
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 · uneditedHCL DRYiCE MyCloud is affected by the use of a broken cryptographic algorithm. An attacker can potentially compromise the confidentiality and integrity of sensitive information.
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 confidenceHCL DRYiCE MyCloud uses a broken cryptographic algorithm for protecting sensitive data, allowing an attacker to potentially decrypt or manipulate information due to cryptographic weaknesses. The vulnerability has a CVSS score of 7.1 (HIGH), indicating significant risk to data confidentiality and integrity.
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= 10.2= 10.4= 10.5= 10.6CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Verify HCL DRYiCE MyCloud installationLocate the MyCloud installation directory or check system services for the MyCloud application processAffected if The application is present on the system
-
Identify installed MyCloud versionCheck the application version from the installation directory, About page, or version file typically found in the product root or bin folderAffected if The version matches 10.2, 10.4, 10.5, or 10.6
-
Locate cryptographic configuration filesSearch for configuration files in the MyCloud data or conf directory that handle encryption, hashing, or secure communication settingsAffected if Configuration files exist and contain encryption-related settings
-
Inspect cryptographic settings for weak algorithmsOpen the identified configuration files and search for references to broken algorithms such as MD5, SHA-1, DES, or weak cipher suitesAffected if Weak cryptographic algorithms (MD5, SHA-1, DES, or similar) are explicitly configured or used in the application settings
A user is affected if HCL DRYiCE MyCloud version 10.2, 10.4, 10.5, or 10.6 is installed and weak cryptographic algorithms are found in the configuration or application settings.
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 dataReplace all instances of broken cryptographic algorithms (e.g., MD5, SHA-1, DES, weak ciphers) with modern strong algorithms such as AES-256, SHA-256+, or TLS 1.2/1.3. Conduct a cryptographic audit across the application and update to vendor-supplied patches if available.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23346 — 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-23346 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