CVE-2013-0687
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 · uneditedThe installer routine in Schneider Electric MiCOM S1 Studio uses world-writable permissions for executable files, which allows local users to modify the service or the configuration files, and consequently gain privileges or trigger incorrect protective-relay operation, via a Trojan horse executable file.
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 confidenceThe installer for Schneider Electric MiCOM S1 Studio sets world-writable permissions on executable files, allowing any local user to modify these binaries. An attacker with local access can replace legitimate executables with malicious Trojan horse programs to escalate privileges or manipulate protective-relay configurations used in power grid operations.
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 dataall versionsCVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:S/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.
-
Verify MiCOM S1 Studio installation existsCheck for the presence of MiCOM S1 Studio installation directory on the system, or query the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'MiCOM S1 Studio' or similar Schneider Electric product entries.Affected if The software is installed on the system.
-
Locate executable files in installation directoryNavigate to the MiCOM S1 Studio installation folder and list all files with .exe extension. Common locations include C:\Program Files\Schneider Electric\MiCOM S1 Studio or C:\Schneider Electric\MiCOM S1 Studio.Affected if Executable files exist in the MiCOM S1 Studio installation folder.
-
Inspect file permissions on executablesRight-click each executable file, select Properties, then view the Security tab. Check the Permissions section for each user/group entry, specifically looking at the 'Modify' or 'Write' permissions.Affected if Any user account other than Administrators or System has Write or Modify permissions to the executable files.
-
Use command-line to confirm world-writable statusOpen a command prompt and run 'icacls "<path_to_executable>"' for each exe file. Review the output for entries showing (CI)(IO)(W) or similar flags indicating world-writable permissions granted to 'Everyone' or 'Users' groups.Affected if The output shows 'Everyone:(I)(W)' or 'Users:(I)(W)' or equivalent world-writable permissions.
If MiCOM S1 Studio is installed and any of its executable files have world-writable permissions granted to non-privileged users, the system is affected by this vulnerability.
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 dataModify file permissions to remove world-writable access from all executables and configuration files, restricting modification to administrator or system accounts only. Consider re-installing with corrected permissions or applying a patch from the vendor.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0687 — 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-0687 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