LiveActive security incident?Get immediate response
CVE Record

CVE-2019-9140: Happypoint mobile application information disclosure vulnerability

When processing Deeplink scheme, Happypoint mobile app 6.3.19 and earlier versions doesn't check Deeplink URL correctly. This could lead to javascript code execution, url redirection, sensitive information disclosure. An attacker can exploit this issue by enticing an unsuspecting user to open a specific malicious URL.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-9140 affects the Happypoint mobile app. A malicious link can abuse the app's deeplink handling because older versions do not validate deeplink URLs correctly. Affected users could face redirects, JavaScript execution, or sensitive information exposure after opening a crafted URL.

Executive priority

Treat this as a focused mobile-app exposure, not a broad infrastructure emergency. Prioritize organizations with managed mobile fleets or employees using Happypoint, then drive version inventory, vendor guidance review, and app update or removal.

Technical view

Happypoint mobile app 6.3.19 and earlier mishandles deeplink URL validation. The CVE maps this to CWE-94 and reports possible JavaScript execution, URL redirection, sensitive information disclosure, and high confidentiality, integrity, and availability impact with user interaction required.

Likely exposure

Exposure is limited to users with Happypoint mobile app 6.3.19 or earlier installed. Risk depends on whether attackers can entice those users to open malicious URLs that trigger the vulnerable deeplink processing.

Exploitation context

The provided sources describe a user-assisted attack using a malicious URL. The record is not listed as KEV, and the bundle provides no evidence of active exploitation or public weaponization.

Researcher notes

Key missing evidence includes the exact fixed version, vendor remediation language, and observed exploitation status. Analysis should remain tied to deeplink validation behavior and user-assisted malicious URL delivery described in the CVE sources.

Mitigation direction

  • Inventory Happypoint mobile app versions across managed devices.
  • Check SPC CLOUD, Happypoint, or KRCERT guidance for fixed versions or advisories.
  • Update or remove Happypoint versions 6.3.19 and earlier where possible.
  • Warn users not to open unexpected links targeting the app.
  • Use MDM controls to restrict vulnerable versions if updates are unavailable.

Validation and detection

  • Confirm whether Happypoint mobile app is installed on managed mobile devices.
  • Identify installed versions and flag 6.3.19 or earlier.
  • Review mobile security telemetry for suspicious redirects or app-link activity.
  • Validate remediation through MDM inventory after updates or removals.
  • Avoid uncontrolled testing of malicious deeplink behavior on production devices.
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.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-9140 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
High
CVSS
7.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.0HighCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.8High
CVSS 3.0 vector shape for CVE-2019-9140Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SPC CLOUDHappypoint mobile app6.3.19Listed
Weakness

CWE details

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

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.