CVE-2020-7490
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 · uneditedA CWE-426: Untrusted Search Path vulnerability exists in Vijeo Designer Basic (V1.1 HotFix 15 and prior) and Vijeo Designer (V6.9 SP9 and prior), which could cause arbitrary code execution on the system running Vijeo Basic when a malicious DLL library is loaded by the Product.
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 confidenceThis is a CWE-426 Untrusted Search Path vulnerability where Vijeo Designer Basic and Vijeo Designer load DLL libraries from untrusted locations, allowing an attacker to place a malicious DLL in a search path location that the application will traverse before finding the legitimate DLL, resulting in arbitrary code execution.
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.0<= 6.2= 1.1= 6.9CVSS 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.
-
Identify installed Vijeo Designer product and versionOpen Windows Control Panel > Programs and Features, or check the installation directory (typically C:\Program Files\Schneider Electric\Vijeo Designer or Vijeo Designer Basic) for version information. You can also right-click the executable and view Properties > Details for the File Version.Affected if The installed version is Vijeo Designer Basic <= 1.0, = 1.1, or Vijeo Designer <= 6.2, = 6.9
-
Confirm product variantDetermine whether you are running Vijeo Designer Basic or Vijeo Designer (the full version) by checking the program name in Programs and Features or the executable name in the installation folder.Affected if Either product variant with the version numbers listed in step 1 is installed
-
Examine system PATH for untrusted directoriesOpen Command Prompt and run 'echo %PATH%' to view the system PATH. Also run 'echo %PATH%' in any command prompt you use to launch the application. Inspect each directory in the PATH for write access by untrusted users.Affected if Any directory in the system or user PATH is writable by non-admin users or located in a shared/network location
-
Inspect application working directory for extraneous DLLsCheck the directory from which you launch Vijeo Designer (the current working directory when the application starts). Look for any DLL files in that location that are not part of the standard installation.Affected if Unexpected DLL files exist in the directory from which the application is launched, or the working directory is a shared/network location
-
Check application installation directory for writable accessVerify file permissions on the Vijeo Designer installation directory (e.g., C:\Program Files\Schneider Electric\Vijeo Designer). Ensure standard users cannot write new files to this location.Affected if Non-privileged users have write permission to the application's installation directory
You are affected if you have Vijeo Designer Basic version 1.0, 1.1, or Vijeo Designer version 6.2 or 6.9 installed AND untrusted directories exist in your PATH or working directory where an attacker could place a malicious DLL.
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 Vijeo Designer Basic version V1.1 HotFix 16 or later, and Vijeo Designer version V6.9 SP10 or later. Alternatively, ensure the application runs from a controlled directory and that no untrusted DLLs can be placed in any directory in the system PATH or application working directory.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7490 — 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-2020-7490 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