CVE-2021-27768
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 · uneditedUsing the ability to perform a Man-in-the-Middle (MITM) attack, which indicates a lack of hostname verification, sensitive account information was able to be intercepted. In this specific scenario, the application's network traffic was intercepted using a proxy server set up in 'transparent' mode while a certificate with an invalid hostname was active. The Android application was found to have hostname verification issues during the server setup and login flows; however, the application did not process requests post-login.
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 · high confidenceAn Android application fails to properly validate hostnames during SSL/TLS certificate verification, allowing an attacker with MITM capabilities to intercept sensitive account credentials. The vulnerability exists specifically in the server setup and login flows where the application accepts connections to invalid hostnames. Post-login requests were not affected.
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< 12.0.9CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 Hcltech Verse app is installedOn the Android device, go to Settings > Apps > Apps, or use ADB command: pm list packages | grep verseAffected if Hcltech Verse application is present on the device
-
Check installed application versionIn Settings > Apps > Hcltech Verse > App info, note the Version or use ADB: dumpsys package com.hcl.verse | grep versionNameAffected if Version displayed is blank, shows a version code, or shows a version lower than 12.0.9 (e.g., 12.0.8, 12.0.7, 11.x, etc.)
-
Verify vulnerability scope - server setup or login flowsDetermine if the device has been used for initial server configuration or to perform login operations within Hcltech Verse. This is a manual review of recent user activity.Affected if The app has been used to configure a new server connection or perform login after installation, since the flaw affects only server setup and login flows (not post-login requests)
-
Confirm affected version rangeCompare the installed version number to the affected range: versions earlier than 12.0.9Affected if Installed version is less than 12.0.9 (e.g., 12.0.8, 12.0.1, 11.0.0, etc.)
User is affected if Hcltech Verse is installed with a version lower than 12.0.9 and the app has been used for server setup or login flows where the SSL/TLS hostname verification flaw could be exploited.
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.
dbcve · scoped12.0.9
Implement proper hostname verification by ensuring all network connections use valid certificate validation, typically by configuring HTTPS clients to verify server certificates against the expected hostname or using standard Android networking libraries with default certificate validation enabled.
Verse Android 12.0.9
- Update the HCL Verse Android application to version 12.0.9 or later from the Google Play Store or your organization's enterprise app store
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27768 — 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-2021-27768 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