CVE-2024-25677
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 Min before 1.31.0, local files are not correctly treated as unique security origins, which allows them to improperly request cross-origin resources. For example, a local file may request other local files through an XML document.
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 confidenceMin browser before 1.31.0 fails to properly enforce the Same-Origin Policy for local file:// URLs, treating all local files as a single origin instead of unique origins. This allows a malicious local HTML file to make XMLHttpRequest or fetch requests to other local files on the system, potentially exfiltrating sensitive data.
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= 1.29.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Min browser installationLocate the Min browser executable or application package on the systemAffected if Min browser version 1.29.0 is installed and running
-
Determine installed version of MinCheck the browser version through its help menu, about dialog, or executable properties - compare against the affected version 1.29.0Affected if The installed version matches 1.29.0 exactly
-
Verify local file access is enabledCheck if the browser allows loading local files via file:// URLs or has a setting that permits local file accessAffected if Local file loading via file:// URLs is permitted in the browser settings
-
Test Same-Origin Policy for file URLsCreate two test HTML files locally and attempt to make an XMLHttpRequest or fetch request from one to the other - if successful without origin errors, the vulnerability is presentAffected if A local HTML file can successfully request content from a different local file using fetch or XMLHttpRequest, indicating the Same-Origin Policy is not properly enforced for file:// URLs
A user is affected if they have Min browser version 1.29.0 installed and use the browser to access local files via file:// URLs, allowing potential cross-file data access.
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 · scopedUpgrade Min browser to version 1.31.0 or later to obtain the fix that correctly treats each local file as a unique security origin.
Min 1.31.0 or later
- Identify the current version of Min browser installed (help/about in the application menu)
- Download Min version 1.31.0 or later from the official GitHub repository (github.com/minbrowser/min)
- Close all instances of the Min browser
- Install the updated version of Min, replacing the existing installation
- Restart Min and verify the new version is running (help/about)
- Test that local files are now properly treated as unique security origins
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25677 — 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-25677 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