CVE-2015-9232 json
The Good for Enterprise application 3.0.0.415 for Android does not use signature protection for its Authentication Delegation API intent.
published 2017-09-20 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-9085
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
The Good for Enterprise application 3.0.0.415 for Android does not use signature protection for its Authentication Delegation API intent. Also, the Good Dynamic application activation process does not attempt to detect malicious activation attempts involving modified names beginning with a com.good.gdgma substring. Consequently, an attacker could obtain access to intranet data. This issue is only relevant in cases where the user has already downloaded a malicious Android application.
Exploit prediction
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- modzero.ch https://www.modzero.ch/advisories/MZ-15-03-GOOD-Auth-Delegation.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/archive/1/536543 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
modzero.ch
/advisories/MZ-15-03-GOOD-Auth-Delegation.txt
exploit, mitigation, third-party-advisory
-
securityfocus.com
/archive/1/536543
exploit, mitigation, third-party-advisory, vdb-entry
-
community.blackberry.com
/community/blogs/blog/2015/10/02/what-you-need-to-know-modzero-insecure-application-coupling
third-party-advisory
Sources
- CVE List CVE-2015-9232
- NVD CVE-2015-9232
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.