CVE-2024-37406
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 · uneditedIn Brave Android prior to v1.67.116, domains in the Brave Shields popup are elided from the right instead of the left, which may lead to domain confusion.
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 confidenceIn Brave Android prior to v1.67.116, the Brave Shields popup UI incorrectly elides (truncates) long domain names from the left side instead of the right side. This means when a domain name is too long to fit in the display, users see the beginning of the domain instead of the end, potentially obscuring the actual domain they are visiting and leading to domain confusion attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Check Brave Android app versionOpen the Brave Android app, tap the menu (three lines) in the bottom right, scroll down to Settings, tap Help, then tap About Brave to see the installed version numberAffected if The displayed version is earlier than v1.67.116 (for example, v1.67.115, v1.66.x, etc.)
-
Verify Brave Shields are enabledTap the lion icon in the address bar or open the Shields popup by tapping the Brave icon in the bottom right corner to access the Brave Shields controlsAffected if Brave Shields are turned ON - this means the vulnerable UI component is active and visible to the user
-
Test domain elision behaviorNavigate to a website with a long subdomain chain such as verylongsubdomainname.example.com in the Brave Android browser, then open the Brave Shields popup and observe how the domain is displayed when it exceeds the popup widthAffected if The domain name displays the beginning of the domain (such as 'verylo...' instead of '...example.com'), truncating from the left side rather than the right
A user is affected if they are running a Brave Android version before v1.67.116 and have Brave Shields enabled, allowing the Shields popup to display truncated domain names from the left side instead of the right.
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.
dbcve · scopedUpdate Brave Android to version v1.67.116 or later to receive the fix for the incorrect domain elision direction in the Shields popup.
Brave Android v1.67.116 or later
- 1. Open the Google Play Store app on your Android device
- 2. Search for "Brave Browser" or "Brave"
- 3. Tap on the Brave browser app from the search results
- 4. If an update is available, tap the "Update" button
- 5. Wait for the update to download and install
- 6. Alternatively, enable auto-updates for Brave in the Play Store to ensure you receive future security patches
- 7. After updating, verify the version by opening Brave, going to Settings > About Brave, and confirming the version is v1.67.116 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37406 — 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-2024-37406 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