dbcve.org
FirefoxWeb browser · Mozilla

CVE-2023-25747

HIGH · 7.5 CVSS v3.1 Published 2023-06-19
Fix available
A fix is available. Upgrade to 110.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 potential use-after-free in libaudio was fixed by disabling the AAudio backend when running on Android API below version 30. *This bug only affects Firefox for Android. Other versions of Firefox are unaffected.* This vulnerability affects Firefox for Android < 110.1.0.

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 confidence

A use-after-free vulnerability exists in libaudio's AAudio backend in Firefox for Android. The vulnerability is triggered when running on Android API versions below 30, where the AAudio backend can cause a use-after-free condition during audio processing. The fix disables the AAudio backend entirely on Android API versions below 30.

MitigationUpdate Firefox for Android to version 110.1.0 or later, which contains the fix to disable the AAudio backend on Android API < 30.

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
FirefoxWeb browser
Affected:< 110.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm Firefox for Android is in use
    Check that the application is Mozilla Firefox for Android (not Firefox Desktop). On the device, go to Settings > Apps > Firefox and verify the package name contains 'android' or check via 'adb shell pm list packages | grep mozilla'.
    Affected if The application is Firefox for Android.
  2. Check installed Firefox for Android version
    On the Android device, go to Settings > Apps > Firefox > App info, or visit about:support in the Firefox URL bar. Note the version number shown.
    Affected if Version is below 110.1.
  3. Check Android API level
    On the Android device, go to Settings > About Phone > Android version, or use 'adb shell getprop ro.build.version.sdk' via command line.
    Affected if API level is below 30 (Android 10 or earlier).
  4. Determine if AAudio backend is active
    Check if audio is being processed through the AAudio backend. This can be confirmed by examining Firefox's audio backend configuration at about:config (if accessible) or by reviewing crash logs for AAudio-related audio processing.
    Affected if AAudio backend is actively handling audio on an affected version and API level.

A user is affected if they are running Firefox for Android version below 110.1 on an Android device with API level below 30, where the AAudio backend is enabled and processing audio.

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.

dbcve · scoped
Upgrade available Upgrade to 110.1 or later
Fixed in 110.1
Interim mitigation

Update Firefox for Android to version 110.1.0 or later, which contains the fix to disable the AAudio backend on Android API < 30.

Recommended fix High confidence

Firefox for Android 110.1.0 or later

  1. Update Firefox for Android to version 110.1.0 or later through the Google Play Store or your device's app update mechanism

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25747 — 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-2023-25747 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