# CVE-2021-27753: Path traversal in "HCL Sametime"

> An attacker can exploit a path traversal vulnerability in the HCL Sametime Android app to read arbitrary files from the device.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6vw3-6qjj-285r

## What is CVE-2021-27753?

CVE-2021-27753 is a medium-severity path traversal vulnerability in "HCL Sametime", published on 21 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

"Sametime Android PathTraversal Vulnerability"

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-27753?

It affects 1 product.


Products: Hcltech Hcl Sametime.

## How do I fix CVE-2021-27753?

No fix has been published for CVE-2021-27753 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-27753 being exploited?

There is no known exploitation of CVE-2021-27753 in the wild and no public exploit code.

## Other vulnerabilities in "HCL Sametime"

- [CVE-2021-27755](https://insights.sbomify.com/CVE-2021-27755/): Path traversal in "HCL Sametime" (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27753 and fix it if it is affected.

What it is: CVE-2021-27753 is a medium-severity path traversal vulnerability in "HCL Sametime", published on 21 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27753 in the wild and no public exploit code.

Affected product: "HCL Sametime". No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-27753/ (Markdown: https://insights.sbomify.com/CVE-2021-27753/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-27753
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-27753
- OSV: https://osv.dev/vulnerability/CVE-2021-27753

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-27753/
Summaries are generated and may contain mistakes; the official description above is the record.