CVE-2024-28131
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 · uneditedEasyRange Ver 1.41 contains an issue with the executable file search path when displaying an extracted file on Explorer, which may lead to loading an executable file resides in the same folder where the extracted file is placed. If this vulnerability is exploited, arbitrary code may be executed with the privilege of the running program. Note that the developer was unreachable, therefore, users should consider stop using EasyRange Ver 1.41.
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 confidenceEasyRange Ver 1.41 suffers from an executable search path vulnerability (binary planting) when displaying extracted files in Windows Explorer. The application loads executables from the same folder as the displayed file without using fully qualified paths, allowing attackers to place malicious executables that get executed with the application's privileges.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Locate EasyRange installationSearch for eastrng.exe or eastrng.exe in common program directories: C:\Program Files\, C:\Program Files (x86)\, or using PowerShell: Get-ChildItem -Path C:\ -Recurse -Filter eastrng.exe -ErrorAction SilentlyContinueAffected if eastrng.exe is found on the system
-
Confirm installed version is 1.41Right-click eastrng.exe, select Properties, then look at the Version tab to read the File Version. Alternatively, run: (Get-Item "C:\Path\To\eastrng.exe").VersionInfo.FileVersionAffected if File version displays as 1.41
-
Verify binary planting behavior existsThis vulnerability is inherent to version 1.41 - the application loads executables from the same folder as displayed files without fully qualified paths. No additional config check needed; version 1.41 specifically exhibits this flaw.Affected if Version is confirmed as 1.41 (the vulnerable behavior is present by design)
If eastrng.exe version 1.41 is present on the system, the environment is affected by CVE-2024-28131 and should be removed.
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 · scopedSince the developer is unreachable and no patch exists, discontinue use of EasyRange Ver 1.41 immediately and migrate to an alternative solution. Verify no instances remain in the environment.
- Discontinue use of EasyRange Ver 1.41 as the developer is unreachable and no fix is available.
- Replace EasyRange with an actively maintained alternative file compression/extraction tool.
- If immediate replacement is not possible, exercise extreme caution when extracting files - never extract to folders that also contain executable files, and scan all extracted files with up-to-date antivirus software before opening.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28131 — 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-28131 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