CVE-2023-47583
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 vulnerabilities exist in TELLUS Simulator V4.0.17.0 and earlier. If a user opens a specially crafted file (X1 or V9 file), information may be disclosed and/or arbitrary code may be executed.
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 TELLUS Simulator when parsing specially crafted X1 or V9 files. These memory access violations can leak sensitive information from process memory and potentially enable arbitrary code execution when the read primitive is combined with other exploitation techniques.
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.17.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.
-
Confirm Fujielectric Tellus is installedLook for TELLUS Simulator in the program files directory (typically C:\Program Files\Fujitsu\Tellus or similar), or check the Windows Programs and Features list for Fujielectric Tellus entries.Affected if TELLUS Simulator is present on the system
-
Identify installed TELLUS versionRight-click the Tellus executable (commonly Tellus.exe or similar main application file), select Properties, and check the Details tab for the Product Version. Alternatively, check any version information displayed within the application's About or Help menu.Affected if The installed version is 4.0.17.0 or lower (any version up to and including 4.0.17.0)
-
Check for presence of X1 or V9 file handlingDetermine if the Tellus installation includes file parsers or libraries capable of opening X1 or V9 file formats. This may be evident from the file type associations, import functionality, or the presence of related file filter modules in the installation directory.Affected if TELLUS can open or import X1 or V9 files, as the vulnerability triggers specifically when parsing these specially crafted files
A user is affected if Fujielectric Tellus version 4.0.17.0 or lower is installed and the application has the ability to parse X1 or V9 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 dataDo not open untrusted X1 or V9 files with TELLUS Simulator. Upgrade to a version newer than V4.0.17.0 when a patched release is available from the vendor.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47583 — 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-47583 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