CVE-2024-30135
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 AEX is potentially impacted by disclosure of sensitive information in the mobile application when a snapshot is taken.
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 AEX mobile application fails to properly protect sensitive information from being disclosed when a user takes a snapshot or screenshot of the app. This is a common mobile vulnerability where the app does not implement screen capture protection controls (such as FLAG_SECURE on Android), allowing sensitive data displayed in the app to be captured in device screenshots.
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.0CVSS 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 if HCL DRYiCE AEX mobile app is installedOn Android: Run 'adb shell pm list packages | grep -i dryice' or check app settings. On iOS: Check installed apps list for 'AEX' or 'Dryice'Affected if The HCL DRYiCE AEX mobile application is present on any managed mobile device
-
Verify the installed version is 10.0On Android: Run 'adb shell dumpsys package com.hcl.dryice.aex' and check versionName/versionCode. On iOS: Check app version in the App Store or device settingsAffected if The installed version equals 10.0 exactly (version 10.0 is affected)
-
Confirm lack of screen capture protection on AndroidAttempt to take a screenshot while the AEX app is displayed - if the screenshot captures the app content without being blocked, the vulnerability is present. Alternatively, decompile the APK and check if FLAG_SECURE is set on sensitive activities in the AndroidManifest.xmlAffected if Screenshots of the app can be taken freely without the app blocking them, indicating FLAG_SECURE is not implemented
A user is affected if they have HCL DRYiCE AEX version 10.0 installed on any mobile device and can capture screenshots of sensitive app content.
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 dataImplement proper screen capture protection mechanisms in the mobile application - on Android this involves setting FLAG_SECURE on sensitive windows/activities, and on iOS ensuring proper snapshot handling to prevent sensitive data exposure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30135 — 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-2024-30135 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