National Payments of India BHIM App 1.3 on Android OTP improper authentication
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in National Payments of India BHIM App 1.3 on Android. Affected by this issue is some unknown functionality of the component OTP Handler. The manipulation leads to improper authentication. This vulnerability is handled as CVE-2017-9819. The attack may be launched remotely. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as critical was found in National Payments of India BHIM App 1.3 on Android (Android App Software). Affected by this vulnerability is an unknown code of the component OTP Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The National Payments Corporation of India BHIM application 1.3 for Android does not properly restrict use of the OTP feature, which makes it easier for attackers to bypass authentication.
The bug was discovered 08/21/2018. The weakness was released 08/24/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2017-9819 since 06/22/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-123210, VDB-123212 and VDB-123213. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/22/2017 🔍08/21/2018 🔍
08/24/2018 🔍
08/24/2018 🔍
08/25/2018 🔍
05/04/2023 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2017-9819 (🔍)
GCVE (CVE): GCVE-0-2017-9819
GCVE (VulDB): GCVE-100-123211
X-Force: 148926
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍
Entry
Created: 08/25/2018 08:31Updated: 05/04/2023 13:25
Changes: 08/25/2018 08:31 (60), 03/18/2020 06:50 (1), 05/04/2023 13:25 (3)
Complete: 🔍
Cache ID: 216:C7E:103
No comments yet. Languages: en.
Please log in to comment.