dbcve.org
AndroidOperating system · Google

CVE-2017-0477

HIGH · 7.8 CVSS v3.0 Published 2017-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A remote code execution vulnerability in libgdx could enable an attacker using a specially crafted file to execute arbitrary code within the context of an unprivileged process. This issue is rated as High due to the possibility of remote code execution in an application that uses this library. Product: Android. Versions: 7.1.1. Android ID: A-33621647.

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 · moderate confidence

A remote code execution vulnerability in libgdx (a cross-platform game development framework) allows attackers to execute arbitrary code by tricking users into opening specially crafted files. The vulnerability resides in how libgdx processes certain file types, enabling code execution within the context of the unprivileged application using the library.

MitigationUpdate libgdx to the latest patched version in all Android applications that incorporate this library. Since this is a library vulnerability, any application using the affected libgdx version is vulnerable until the library is updated.

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
AndroidOperating system
Affected:= 7.0= 7.1.0= 7.1.1

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if your Android application uses libgdx
    Inspect the application's build configuration files (build.gradle, pom.xml, or similar) for libgdx dependencies. Also check the libs/ or app/libs/ directories for gdx.jar or similar libgdx library files.
    Affected if libgdx library is included in the application dependencies or project files
  2. Determine the installed libgdx version
    Check the version string in the libgdx JAR file (typically in the filename like gdx-1.9.x.jar) or in the build configuration file's dependency declaration. You can also decompile the APK and inspect the classes in the com.badlogic.gdx package for version information.
    Affected if The libgdx version matches or falls within the vulnerable version range for this CVE
  3. Verify the application runs on affected Android versions
    Check the application's target SDK and minimum SDK settings in AndroidManifest.xml or build.gradle. The vulnerability affects Android 7.0 (API 24), 7.1.0 (API 25), and 7.1.1 (API 25) when using the vulnerable libgdx version.
    Affected if The application targets or runs on Android 7.0, 7.1.0, or 7.1.1 with a vulnerable libgdx version in use
  4. Confirm if the application processes external file types
    Review the application's code for file loading functionality, particularly any handlers for file types that libgdx processes (such as images, audio, or custom asset files loaded from external sources). Check for uses of Gdx.files or AssetManager loading files from untrusted sources.
    Affected if The application loads file types processed by libgdx from external or untrusted sources

Your environment is affected if you have an Android application using a vulnerable libgdx version that processes file types from external sources, particularly when running on Android 7.0, 7.1.0, or 7.1.1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libgdx to the latest patched version in all Android applications that incorporate this library. Since this is a library vulnerability, any application using the affected libgdx version is vulnerable until the library is updated.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-0477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-0477 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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