CVE-2013-0665
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 · uneditedSchweitzer Engineering Laboratories (SEL) AcSELerator QuickSet before 5.12.0.1 uses weak permissions for its Program Files directory, which allows local users to replace executable files, and consequently gain privileges, via standard filesystem operations.
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 confidenceSEL AcSELerator QuickSet before version 5.12.0.1 stores its executable files in a Program Files directory with weak permissions that allow local users to modify or replace files. A local unprivileged user can replace legitimate executables with malicious ones, achieving privilege escalation when administrators run the software.
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<= 5.12.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
- Local
- Complexity
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:H/Au:N/C:C/I:C/A:C
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 if AcSELerator QuickSet is installedLook for the product in Add/Remove Programs (Programs and Features), or check the typical installation path C:\Program Files\SEL\AcSELerator QuickSet or C:\Program Files (x86)\SEL\AcSELerator QuickSet. Also check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named AcSELerator QuickSet.Affected if The software is not installed on the system.
-
Determine the installed version of AcSELerator QuickSetRight-click the QuickSet executable (typically named AcSELerator.exe or similar in the installation folder), select Properties, and examine the File Version or Product Version field in the Details tab. Alternatively, check the Uninstall registry entry for the DisplayVersion value.Affected if The installed version is 5.12.0 or any earlier version (versions <= 5.12.0 are affected).
-
Identify the installation directory permissionsOpen the folder where AcSELerator QuickSet is installed. Right-click the folder, select Properties, go to the Security tab, and examine the permissions for Users or other non-administrator groups. Use the command 'icacls "C:\Program Files\SEL\AcSELerator QuickSet"' or the equivalent path to list effective permissions.Affected if Non-administrator users (such as the Users group or authenticated users) have Write or Modify permissions to the installation directory or its executable files.
-
Verify if low-privilege users can replace executablesAs a test, attempt to create or modify a file in the QuickSet installation directory using a standard user account (non-admin). Alternatively, run 'icacls "<installation_path>\*.exe"' to see which users have write access to executable files.Affected if Standard users can write to or replace the executable files in the QuickSet installation folder.
The system is affected if AcSELerator QuickSet version 5.12.0 or earlier is installed AND non-administrative users have write access to the QuickSet installation directory or its executable files.
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 AcSELerator QuickSet to version 5.12.0.1 or later, which contains the proper permission fixes. Until patched, restrict write access to the QuickSet installation directory to administrators only.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0665 — 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-2013-0665 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