# CVE-2021-40527: Hardcoded credentials in n/a

> Remote attackers can access sensitive developer files in AWS S3 by extracting plain-text credentials from the Peloton mobile application.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pp98-w696-5gp2

## What is CVE-2021-40527?

CVE-2021-40527 is a high-severity vulnerability in n/a, published on 25 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Exposure of senstive information to an unauthorised actor in the "com.onepeloton.erlich" mobile application up to and including version 1.7.22 allows a remote attacker to access developer files stored in an AWS S3 bucket, by reading credentials stored in plain text within the mobile application.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Onepeloton Peloton.

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

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

## Is CVE-2021-40527 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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