CVE-2019-1010101
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 · uneditedAkeo Consulting Rufus 3.0 and earlier is affected by: Insecure Permissions. The impact is: arbitrary code execution with escalation of privilege. The component is: Executable installer, portable executable (ALL executables available). The attack vector is: CWE-29, CWE-377, CWE-379.
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 · moderate confidenceAkeo Consulting Rufus 3.0 and earlier contains insecure permissions in its executable installer and portable executable files. This allows unprivileged users to modify the executable files, potentially enabling them to replace the legitimate executable with a malicious version and achieve arbitrary code execution with privilege escalation.
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<= 3.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 Rufus installation and versionSearch for Rufus executables (e.g., rufus.exe) on the system and check file properties to determine the version number. Common locations: Program Files, Program Files (x86), or user's Downloads folder. Right-click the executable, select Properties, and view the Details tab for version info.Affected if Rufus version is 3.0 or earlier (or version cannot be determined but the executable exists)
-
Locate all Rufus executable filesUse file search to find all instances of rufus.exe on the system, including portable versions. Search entire system or known application directories.Affected if Any Rufus executable exists on the system
-
Check executable file permissionsRight-click each rufus.exe file, select Properties, go to Security tab, and examine the permissions for Users and other non-admin groups. Look for Write or Modify permissions granted to standard users.Affected if Non-admin users have Write or Modify permissions on any Rufus executable
-
Verify world-writable statusOpen Command Prompt with standard user privileges (non-admin account), navigate to the folder containing rufus.exe, and attempt to delete or rename the file. Alternatively, use icacls rufus.exe to view effective permissions.Affected if A non-admin user can successfully modify, delete, or rename the Rufus executable
The environment is affected if Rufus version 3.0 or earlier is installed AND non-privileged users have write/modify permissions on any Rufus executable file, allowing potential replacement with malicious code.
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.
From vendor dataUpdate to a version of Rufus later than 3.0 and ensure executable files have restrictive permissions (least privilege) to prevent unauthorized modification by unprivileged users.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1010101 — 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-2019-1010101 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