# CVE-2017-9818: Weak cryptography in n/a

> The BHIM Android app uses a weak four-digit passcode, allowing attackers to easily guess it and gain unauthorized access to user accounts.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 24 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qmpq-mwc3-g6hf

## What is CVE-2017-9818?

CVE-2017-9818 is a high-severity vulnerability in n/a, published on 24 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The National Payments Corporation of India BHIM application 1.3 for Android relies on a four-digit passcode, which makes it easier for attackers to obtain access.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2017-9818?

It affects 1 product.


Products: Npci Bharat Interface for Money \(Bhim\).

## How do I fix CVE-2017-9818?

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

## Is CVE-2017-9818 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9819](https://insights.sbomify.com/CVE-2017-9819/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-9820](https://insights.sbomify.com/CVE-2017-9820/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-9821](https://insights.sbomify.com/CVE-2017-9821/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9818 and fix it if it is affected.

What it is: CVE-2017-9818 is a high-severity vulnerability in n/a, published on 24 Aug 2018. 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-2017-9818 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-2017-9818/ (Markdown: https://insights.sbomify.com/CVE-2017-9818/index.md)
```

## Sources

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

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