# CVE-2024-35537: Weak cryptography in n/a

> Attackers can decrypt sensitive information due to insecure RSA key handling in the TVS Connect mobile application.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 21 Jun 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-cg88-8hv4-jpxm

## What is CVE-2024-35537?

CVE-2024-35537 is a high-severity vulnerability in n/a, published on 21 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TVS Motor Company Limited TVS Connect Android v4.6.0 and IOS v5.0.0 was discovered to insecurely handle the RSA key pair, allowing attackers to possibly access sensitive information via decryption.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Tvsmotor Tvs Connect.

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

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

## Is CVE-2024-35537 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35537 is a high-severity vulnerability in n/a, published on 21 Jun 2024. 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-2024-35537 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-2024-35537/ (Markdown: https://insights.sbomify.com/CVE-2024-35537/index.md)
```

## Sources

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

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