LiveActive security incident?Get immediate response
CVE Record

CVE-2018-17108: The SBIbuddy (aka com.sbi.erupee) application 1.41 and 1.42 for Android might allow attackers to perform Ac...

The SBIbuddy (aka com.sbi.erupee) application 1.41 and 1.42 for Android might allow attackers to perform Account Takeover attacks by intercepting a security-question response during the initial configuration of the application.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-17108 concerns older Android versions of the SBIbuddy app. The report says an attacker might take over an account by intercepting a security-question response during first-time setup. Public metadata is sparse, with no CVSS score or named vendor fix in the provided sources.

Executive priority

Prioritize only if your organization supports users or devices with this legacy SBIbuddy Android app. For exposed populations, account takeover impact makes removal or upgrade verification urgent despite incomplete scoring data. If no affected app versions exist, business urgency is low.

Technical view

The issue is described as an authentication/setup weakness in SBIbuddy, also identified as com.sbi.erupee, versions 1.41 and 1.42 for Android. During initial configuration, a security-question response may be interceptable, potentially enabling account takeover. No CWE, CVSS vector, patch detail, or full affected-product record is supplied.

Likely exposure

Exposure appears limited to Android devices using SBIbuddy versions 1.41 or 1.42, especially during initial app configuration. The CVE record’s structured affected-product data is incomplete, so confirm package name and version directly from device or MDM inventory.

Exploitation context

The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. The public description states account takeover might be possible, but does not provide validated exploit prevalence, attack complexity, or remediation status.

Researcher notes

Evidence is thin: the CVE description and one referenced PDF identify the scenario, but structured affected data is n/a and no official fix is named in the bundle. Treat this as a historical mobile authentication weakness requiring inventory-led validation, not broad internet exposure.

Mitigation direction

  • Inventory managed Android devices for com.sbi.erupee versions 1.41 and 1.42.
  • Retire or remove affected app versions where found.
  • Check SBI or app-store guidance for supported replacements or fixed releases.
  • Avoid using affected versions for new account setup until guidance is confirmed.
  • Monitor impacted accounts for suspicious setup or recovery activity.

Validation and detection

  • Confirm whether any managed devices have SBIbuddy installed.
  • Record exact package name and version from MDM or device inventory.
  • Review vendor or app-store release history for remediation guidance.
  • Check helpdesk or fraud reports for suspicious account setup events.
  • Document uncertainty because CVSS, CWE, and patch data are absent.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-17108 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.