# CVE-2018-15661: Auth bypass in n/a

> Attackers with accessibility and SMS permissions can bypass authentication via the Forgot Password screen in the Ola Money Android app.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Aug 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qm79-2xvm-7f2r

## What is CVE-2018-15661?

CVE-2018-15661 is a high-severity authentication bypass vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in the Ola Money (aka com.olacabs.olamoney) application 1.9.0 for Android. If an attacker controls an application with accessibility permissions and the ability to read SMS messages, then the Forgot Password screen can be used to bypass authentication. NOTE: the vendor does not agree that this is a security issue requiring a fix

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-15661?

It affects 1 product.


Products: Olacabs Ola Money.

## How do I fix CVE-2018-15661?

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

## Is CVE-2018-15661 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15661 and fix it if it is affected.

What it is: CVE-2018-15661 is a high-severity authentication bypass vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-15661 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-2018-15661/ (Markdown: https://insights.sbomify.com/CVE-2018-15661/index.md)
```

## Sources

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

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