CVE-2023-47582
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 · uneditedAccess of uninitialized pointer vulnerability exists in TELLUS V4.0.17.0 and earlier and TELLUS Lite V4.0.17.0 and earlier. If a user opens a specially crafted file (X1, V8, 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 · high confidenceAn uninitialized pointer vulnerability in TELLUS V4.0.17.0 and earlier allows attackers to execute arbitrary code or disclose information via specially crafted X1, V8, or V9 files during parsing.
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.0<= 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.
-
Identify if Tellus or Tellus Lite is installedCheck the system for installation of Fujielectric Tellus or Tellus Lite software. Look in Program Files for 'Fujielectric Tellus' folder or check the Windows registry under HKLM\Software\Fujielectric or HKLM\Software\Wow6432Node\Fujielectric for Tellus entries.Affected if Either Tellus or Tellus Lite is found on the system
-
Determine the installed version of TellusLocate the Tellus executable (typically tellus.exe or telluslite.exe) and check its file properties, or run 'tellus.exe -v' or 'telluslite.exe -v' from the command line if supported, or look in the About section within the application.Affected if The version is 4.0.17.0 or earlier
-
Check if X1, V8, or V9 file parsing is usedSearch the filesystem for any X1, V8, or V9 files, or review recent file access logs if available, to determine if these file types have been opened or are present on the system.Affected if X1, V8, or V9 files exist on the system or have been recently opened
-
Verify if files from untrusted sources are processedReview the source of X1, V8, or V9 files. Check if any were obtained from external sources, email attachments, downloads, or network shares outside the organization.Affected if Any X1, V8, or V9 files originate from untrusted or unknown sources
A system is affected if Fujielectric Tellus or Tellus Lite version 4.0.17.0 or earlier is installed and the system processes X1, V8, or V9 files, especially from untrusted sources.
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 TELLUS and TELLUS Lite to a version later than V4.0.17.0; avoid opening untrusted X1, V8, or V9 files until the update is applied.
- Consultation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47582 — 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-47582 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