Safeguard
Vulnerability Analysis•

CVE-2018-9477: High Auth Bypass in Android Developer Options

CVE-2018-9477: High Auth Bypass in Android Developer Options. Fixed at patch level 2018-09-01 or later. Check device patch levels and update.

Safeguard Security Team
3 min read

CVE-2018-9477 is a high severity authentication bypass caused by a missing permission check in the development options section of the Settings app. NVD scores it 7.8. Google fixes it at security patch level 2018-09-01 or later. Install the device update that reaches that level.

What's affected

  • Product: Android, in the development options section of the Settings app.
  • Releases listed by the bulletin: 8.0 and 8.1. The NVD product list shows only some Android releases, so treat the bulletin as the fuller list.
  • Fixed in: security patch level 2018-09-01 or later, according to the Android Security Bulletin for September 2018.
  • Impact in the record: local escalation of privilege, user interaction needed.
  • Severity: NVD scores it 7.8 High (vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The bulletin lists it as High, type EoP. The two ratings agree.
  • Weakness classes: CWE-862 (Missing Authorization), CWE-294 (Authentication Bypass by Capture-replay).

How to check if you're exposed

  • On the device, open Settings and find the Android security patch level, usually under About phone. The exact path varies by manufacturer. A date earlier than 2018-09-01 means the fix is not present.
  • With a USB debugging connection, run adb shell getprop ro.build.version.security_patch. It prints the patch level as a date. You need 2018-09-01 or later.
  • For a fleet, export the patch level from your mobile device management console and filter for dates earlier than 2018-09-01.
  • Match each device against the release list above. Devices on releases outside it are not named for this CVE, but check them against the other entries in the same bulletin.

What to do now

  1. Identify every Android device in scope and record its current security patch level.
  2. Roll out the manufacturer or carrier update that reaches 2018-09-01 or later. Google publishes the fixes, but each device maker decides when its devices receive them.
  3. For devices that no longer receive updates, plan replacement or limit what they can reach, such as corporate mail and internal apps.
  4. Write the update policy down, with a maximum patch age, and report exceptions.

Why it matters

Only Android 8.0 and 8.1 are listed. The record carries two weakness tags, missing authorization and authentication bypass by capture-replay. The text only says a permission check was missing.

Developer options expose settings that normally require extra steps, such as a lock screen confirmation or an unlock. If one of those paths lacks its check, a person or app with brief physical or local access can change what the device allows. Treating settings screens as protected resources is the lesson. The record's KEV flag is false, so CISA does not list it as exploited. The bulletin says Google had no reports of active customer exploitation or abuse of the newly reported issues in it. That is the absence of a report in the sources read, not proof that no one has tried.

Quick check

Does this need physical access?

The vector is local with user interaction, which usually implies access to the device. The record does not give more detail.

Which patch level should I look for?

The Android Security Bulletin for September 2018 places this fix at 2018-09-01. Any date at or after 2018-09-01 includes it. Some makers ship it under a different update name, so check the date.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.