CVE-2023-35127
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 · uneditedStack-based buffer overflow may occur when Fuji Electric Tellus Lite V-Simulator parses a specially-crafted input 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 · moderate confidenceA stack-based buffer overflow vulnerability exists in Fuji Electric Tellus Lite V-Simulator when parsing specially-crafted input files. The overflow occurs due to insufficient bounds checking during file parsing, allowing an attacker to overwrite stack memory and potentially execute arbitrary code or cause a denial of service.
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.19.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.
-
Locate the Tellus Lite V-Simulator installationSearch for the Tellus Lite V-Simulator executable (typically named TellusLiteV.exe or similar) in program directories such as C:\Program Files\FujiElectric or C:\Program Files (x86)\FujiElectricAffected if The executable is found on the system
-
Determine the installed versionRight-click the executable, select Properties, and check the Details tab for the File Version or Product Version field. Alternatively, right-click the executable and select Properties > Digital Signatures to verify the signer is Fuji ElectricAffected if The version displayed is lower than 4.0.19.0
-
Confirm file parsing functionality is in useVerify the software is capable of loading or parsing input project files, configuration files, or simulation files. This is a core feature of the simulator and is enabled by default upon installationAffected if The software is installed and functional for parsing input files (this is the default state)
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.
dbcve · scoped4.0.19.0
Avoid opening untrusted or unverified input files with Tellus Lite V-Simulator. Monitor vendor advisories for patches and apply them promptly. Consider network segmentation to limit exposure of systems running this software.
4.0.19.0
- Obtain the latest version of Fuji Electric Tellus Lite V-Simulator (version 4.0.19.0 or later) from the official vendor source at felib.fujielectric.co.jp
- Uninstall the current version of Tellus Lite V-Simulator
- Install the updated version 4.0.19.0 or later
- Restart any running instances of the application
- Verify the installation by checking the software version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35127 — 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-2023-35127 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