LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19981: Amazon AWS SDK <=2.8.5 for Android uses Android SharedPreferences to store plain text AWS STS Temporary Cre...

Amazon AWS SDK <=2.8.5 for Android uses Android SharedPreferences to store plain text AWS STS Temporary Credentials retrieved by AWS Cognito Identity Service. An attacker can use these credentials to create authenticated and/or authorized requests. Note that the attacker must have "root" privilege access to the Android filesystem in order to exploit this vulnerability (i.e. the device has been compromised, such as disabling or bypassing Android's fundamental security mechanisms).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Android apps using Amazon AWS SDK for Android 2.8.5 or earlier may store temporary AWS Cognito credentials in plaintext SharedPreferences. If an attacker already has root-level access to the device filesystem, those credentials could be reused to make AWS requests allowed by the app’s Cognito identity permissions.

Executive priority

Treat this as a moderate mobile cloud-credential exposure issue. Prioritize affected apps that grant broad AWS permissions or run in environments where rooted devices are possible. The root-access prerequisite lowers urgency compared with remotely exploitable flaws.

Technical view

The CVE describes plaintext storage of AWS STS temporary credentials retrieved through AWS Cognito Identity Service by AWS SDK for Android versions up to 2.8.5. The relevant component is CognitoCachingCredentialsProvider. Exploitation requires root access to the Android filesystem, meaning normal Android app sandboxing must already be bypassed.

Likely exposure

Exposure is limited to Android applications that include AWS SDK for Android 2.8.5 or earlier and use Cognito-backed temporary credentials. Business impact depends on the permissions granted to the associated Cognito identities and whether rooted or otherwise compromised devices are in scope.

Exploitation context

The source states an attacker must already have root privilege access to the Android filesystem. No KEV listing or provided source indicates active exploitation. The vulnerability is primarily a post-compromise credential exposure issue, not a remote initial-access flaw.

Researcher notes

Evidence is limited to the CVE description, AWS SDK Android API documentation, and referenced screenshots. The provided sources do not include CVSS, CWE, a named patch version, or confirmed exploitation. Avoid assuming affected products beyond AWS SDK for Android <=2.8.5.

Mitigation direction

  • Inventory Android apps using AWS SDK for Android 2.8.5 or earlier.
  • Check AWS vendor guidance for fixed or supported SDK versions.
  • Upgrade affected apps away from vulnerable SDK versions where confirmed by vendor guidance.
  • Restrict Cognito IAM roles to least privilege.
  • Monitor Cognito and STS activity for anomalous authenticated requests.

Validation and detection

  • Review Android dependency manifests for AWS SDK for Android versions <=2.8.5.
  • Confirm whether the app uses CognitoCachingCredentialsProvider or Cognito temporary credentials.
  • Assess permissions granted to affected Cognito identity roles.
  • Check whether enterprise mobile policy allows rooted or jailbroken Android devices.
  • Review cloud logs for unusual Cognito or STS credential activity.
Prepared
Confidence
medium
Sources
6

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-19981 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
5Source 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.