CVE-2022-20499

What it actually does

Uncaught exceptions during parsing of stored PasspointConfiguration data in Android result in persistent local denial of service without requiring additional privileges or user interaction.

Why it matters to the business

Affected Android devices can become repeatedly unusable after reboot or configuration load, leading to downtime, support costs, and potential loss of device availability for end users or fleets.

How an attack unfolds

An attacker with local access supplies or modifies a stored Passpoint configuration containing malformed data; when the system attempts to validate or load the config at boot or runtime, unhandled errors crash the relevant process, causing persistent DoS until the config is cleared or the device is reset.

How to fix it

Apply the latest Android security updates for versions 12, 12L, and 13 that address parsing errors in PasspointConfiguration.java; where updates are unavailable, disable Passpoint/Wi-Fi features or wipe affected configuration data to restore functionality.

How to confirm the fix worked

Confirm devices are running patched Android builds; test by loading known-malformed Passpoint configs and verifying the system no longer crashes persistently; review release notes for A-246539931 fixes.

Typical attack path

1. Obtain local access on the target Android device
2. Place or modify a malformed Passpoint configuration file in the expected storage location
3. Trigger system parsing of stored configurations (automatic at boot or on Wi-Fi events)
4. Uncaught exception causes process crash and persistent DoS state

How to detect it

Search device and system logs for repeated crashes or exceptions originating from PasspointConfiguration validation routines; look for artifacts of malformed configuration files in Wi-Fi or Passpoint storage directories after unexpected reboots or service restarts.

• PasspointConfiguration.java
• validateForCommonR1andR2
• uncaught exception in config parsing
• /data/misc/wifi/passpoint

What your security team should do

• Prioritize patching all Android 12/12L/13 devices to the latest vendor security update
• Monitor for repeated system crashes tied to Passpoint or configuration parsing in device logs
• Consider disabling Passpoint provisioning on managed devices until updates are applied