Samsung KNOX 1.0 uses a weak eCryptFS Key generation algorithm, which makes it easier for…
Priority LOW 22CWE-200Published · Updated
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-200.
Summary
Samsung KNOX 1.0 uses a weak eCryptFS Key generation algorithm, which makes it easier for local users to obtain sensitive information by leveraging knowledge of the TIMA key and a brute-force attack.
Why it matters now
EPSS 0.00439 38th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2016-1919
- 2026-10-03 Alias added: GHSA-xjjc-8jjh-rwv3
References
More Samsung Knox vulnerabilities
- TI-2016-03397 ClipboardDataMgr in Samsung KNOX 1.0.0 and 2.3.0 does not properly check the caller… CVSS 3.0MEDIUM 5.5
- TI-2016-01758 Samsung KNOX 1.0.0 uses the shared certificate on Android, which allows local users to… CVSS 3.0MEDIUM 5.5
- TI-2019-04781 Improper access control in Samsung Knox CVSS 3.1MEDIUM 4.3
Sources
- CVE-2016-1919 · CVE Program
- CVE-2016-1919 · NVD
- FIRST EPSS
- GHSA-xjjc-8jjh-rwv3 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences