# CVE-2024-42496: Hardcoded credentials in Smart-tab Android app

> An attacker with physical access can retrieve plaintext stored credentials to spoof the device and access external services.

- **Severity:** Low 2.4 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2024
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-p6vx-r8hx-hcq7

## What is CVE-2024-42496?

CVE-2024-42496 is a low-severity vulnerability in TECHNO SUPPORT COMPANY Smart-tab Android app, published on 30 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Smart-tab Android app installed April 2023 or earlier contains an issue with plaintext storage of a password. If this vulnerability is exploited, an attacker with physical access to the device may retrieve the credential information and spoof the device to access the related external service.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2024-42496?


## How do I fix CVE-2024-42496?

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

## Is CVE-2024-42496 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42496 and fix it if it is affected.

What it is: CVE-2024-42496 is a low-severity vulnerability in TECHNO SUPPORT COMPANY Smart-tab Android app, published on 30 Sep 2024. 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-2024-42496 in the wild and no public exploit code.

Affected product: TECHNO SUPPORT COMPANY Smart-tab Android app. 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-2024-42496/ (Markdown: https://insights.sbomify.com/CVE-2024-42496/index.md)
```

## Sources

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

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