CVE-2017-13102
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGameloft Asphalt Xtreme: Offroad Rally Racing, 1.6.0, 2017-08-13, iOS application uses a hard-coded key for encryption. Data stored using this key can be decrypted by anyone able to access this key.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe iOS application Gameloft Asphalt Xtreme embeds a hard-coded encryption key directly in the application code. Attackers can reverse-engineer the application to extract this key and decrypt any data that was encrypted using it.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of Gameloft Asphalt XtremeOn the iOS device, navigate to Settings > Apps > Gameloft Asphalt Xtreme, or use iTunes/Finder to view app information and locate the version numberAffected if Version is 1.6.0 exactly
-
Extract the application binaryUse a jailbroken device or IPA extraction tool to obtain the .ipa file, then unzip to locate the main executable binary (typically named AsphaltXtreme or similar)Affected if Binary extraction succeeds and the app is present
-
Search for hardcoded cryptographic keys in the binaryUse strings command or a hex editor to scan the binary for sequences matching encryption key patterns (look for Base64 strings of appropriate length, or explicit key literals such as 'key=', 'encryptionKey=', or similar variable names containing cryptographic material)Affected if A hardcoded string resembling an encryption key (typically 16, 24, or 32 bytes for AES) is found embedded in the binary code section
-
Verify the key is used for data encryptionStatic analysis: use disassemblers (e.g., IDA Pro, Hopper) or decompilers to trace references to the identified hardcoded string and confirm it is passed to encryption functions (CommonCrypto, CCCrypt, or similar cryptographic APIs)Affected if The hardcoded string is called by encryption/decryption functions and used to encrypt game data
The environment is affected if Gameloft Asphalt Xtreme version 1.6.0 is installed and a hardcoded encryption key is present in the application binary, allowing decryption of any data encrypted with that key.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the hardcoded encryption key with properly secured key management, such as iOS Keychain storage, and re-encrypt any previously encrypted data using the new secure key.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-13102 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data