CVE-2023-5299
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 user with a standard account in Fuji Electric Tellus Lite may overwrite files in the system.
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 confidenceThis vulnerability in Fuji Electric Tellus Lite allows authenticated standard users to overwrite arbitrary files on the system, likely due to insufficient authorization checks on file write operations. This could enable privilege escalation or system compromise depending on which files can be overwritten.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Tellus Lite V Simulator versionOpen the application and navigate to Help > About, or check the program files directory for version information in the executable propertiesAffected if Version is displayed as less than 4.0.19.0
-
Confirm user account type in useCheck the Windows user account running the application - whether it is a standard user account versus an administrator account by viewing User Accounts in Control PanelAffected if Running as an authenticated standard (non-admin) user account
-
Verify file write capability to system directoriesAttempt to write a test file to a protected system directory (such as C:\Windows\System32) using the application's file save functionalityAffected if Standard users can successfully write files outside the application's designated working directory
-
Inspect application file operation logsReview any application logs or audit trails that record file write operations initiated by standard usersAffected if Logs show file write operations targeting paths outside allowed directories
-
Check for unauthorized file modification indicatorsCompare known system files or configuration files against known-good baselines to detect any unexpected modificationsAffected if System files have been modified by the standard user account context
You are affected if Tellus Lite V Simulator version is below 4.0.19.0 AND standard (non-administrator) user accounts can write files to locations outside the application's intended working directory.
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
Implement proper file permission and authorization controls to prevent standard users from overwriting system files; restrict file write operations to only permitted directories and validate user permissions before file operations.
Tellus Lite V Simulator version 4.0.19.0 or later
- 1. Identify the current version of Tellus Lite V Simulator installed on the system
- 2. Download Tellus Lite V Simulator version 4.0.19.0 or later from the official Fujielectric source (felib.fujielectric.co.jp)
- 3. Backup any existing project files and configurations before upgrading
- 4. Run the installer for version 4.0.19.0 or later
- 5. Follow the installation prompts to complete the upgrade
- 6. Verify the installed version is 4.0.19.0 or higher
- 7. Test that standard account users can no longer overwrite system files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5299 — 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-5299 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