CVE-2021-27755
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 · unedited"Sametime Android potential path traversal vulnerability when using File class"
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 confidenceA path traversal vulnerability exists in the Sametime Android application where user-controlled input is used with the Java File class without proper sanitization. This could allow an attacker to access files outside the intended directory by using '../' sequences in file paths.
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< 11.6.5CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Check the installed Sametime Android app versionOn the Android device, go to Settings > Apps > find HCL Sametime (or HCL Sametime Android), tap on it, and view the Version information displayed under the app nameAffected if The version shown is below 11.6.5 (for example, 11.6.0, 11.5.x, or any version starting with a number less than 11)
-
Verify the file handling capability is presentOpen the Sametime app and confirm that file attachment, file sharing, or file transfer features are accessible or have been used (typically found in chat or meeting options)Affected if The app has file handling functionality and the version from step 1 is below 11.6.5
-
Confirm the app receives external input for file operationsCheck if the Sametime app accepts file paths, attachments from external sources, or user-provided filenames through its interface (such as uploading a file with a custom name)Affected if The app processes user-supplied file paths and the version is below 11.6.5
The environment is affected if the HCL Sametime Android application is installed at a version lower than 11.6.5 and includes file handling functionality that accepts user-controlled input.
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 · scoped11.6.5
Implement input validation and path canonicalization when using the File class - validate that resolved paths remain within expected directories and sanitize special characters like '../' before file operations.
HCL Sametime 11.6.5
- 1. Check the current installed version of HCL Sametime Android on affected devices.
- 2. Plan for upgrade during a maintenance window.
- 3. Back up any locally stored data if applicable.
- 4. Upgrade HCL Sametime Android to version 11.6.5 or later.
- 5. Verify the upgrade was successful and the application functions normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27755 — 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-27755 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