CVE-2021-22655
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 · uneditedMultiple out-of-bounds read issues have been identified in the way the application processes project files, allowing an attacker to craft a special project file that may allow arbitrary code execution on the Tellus Lite V-Simulator and V-Server Lite (versions prior to 4.0.10.0).
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 confidenceMultiple out-of-bounds read vulnerabilities exist in the project file processing functionality of Tellus Lite V-Simulator and V-Server Lite. An attacker can craft malicious project files that trigger these out-of-bounds reads, potentially leading to arbitrary code execution on affected systems.
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< 4.0.10.0< 4.0.10.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
- 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.
-
Check if Fujielectric V Server Lite is installedLook for V Server Lite in the Windows Add/Remove Programs list, or check common installation directories such as C:\Program Files\Fujielectric or C:\Program Files (x86)\Fujielectric for executable files named VServerLite.exe or similar.Affected if The software is installed and the installed version is less than 4.0.10.0
-
Check if Fujielectric V Simulator Lite is installedLook for V Simulator Lite in the Windows Add/Remove Programs list, or check common installation directories such as C:\Program Files\Fujielectric or C:\Program Files (x86)\Fujielectric for executable files named VSimulatorLite.exe or similar.Affected if The software is installed and the installed version is less than 4.0.10.0
-
Determine the installed version numberRight-click the executable file (VServerLite.exe or VSimulatorLite.exe) and select Properties, then check the Details tab for the File Version or Product Version field.Affected if The version displayed is lower than 4.0.10.0 or the version field is empty or cannot be determined (which may indicate an older unpatched build).
-
Verify project file processing is usedExamine whether the software has been used to open or create project files (.vprj, .vspj, or similar project file extensions specific to this product). Check recent files or project directories associated with the installation.Affected if The software processes project files and the version is below 4.0.10.0.
You are affected if either V Server Lite or V Simulator Lite is installed with a version lower than 4.0.10.0 and the software is used to process project 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 data4.0.10.0
Upgrade to version 4.0.10.0 or later. Avoid opening untrusted project files from unknown sources.
- Consultation2.0 h
- Implementation2.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22655 — 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-2021-22655 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