# CVE-2021-26833: Information disclosure in n/a

> Local attackers can read stored JWT tokens from the TimelyBills mobile app to access user accounts due to insufficient cache clearing.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f965-7gr5-p9j3

## What is CVE-2021-26833?

CVE-2021-26833 is a medium-severity vulnerability in n/a, published on 6 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cleartext Storage in a File or on Disk in TimelyBills <= 1.7.0 for iOS and versions <= 1.21.115 for Android allows attacker who can locally read user's files obtain JWT tokens for user's account due to insufficient cache clearing mechanisms. A threat actor can obtain sensitive user data by decoding the tokens as JWT is signed and encoded, not encrypted.

Weakness: CWE-459 (Incomplete Cleanup)

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

It affects 1 product.


Products: Timelybills Timelybills.

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

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

## Is CVE-2021-26833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-26833 is a medium-severity vulnerability in n/a, published on 6 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-26833 in the wild and no public exploit code.

Affected product: n/a. 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-26833/ (Markdown: https://insights.sbomify.com/CVE-2021-26833/index.md)
```

## Sources

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

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