dbcve.org
TellusApplication · Fujielectric

CVE-2023-47580

HIGH · 7.8 CVSS v3.1 Published 2023-11-15
Fix available
A fix is available. Upgrade to after 4.0.17.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Multiple improper restriction of operations within the bounds of a memory buffer issues exist 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 confidence

Buffer overflow vulnerabilities in TELLUS V4.0.17.0 and earlier and TELLUS Lite V4.0.17.0 allow arbitrary code execution via specially crafted X1, V8, or V9 files. The improper bounds checking during file parsing permits both information disclosure and code execution.

MitigationUpdate to a version newer than V4.0.17.0 when released by the vendor. Do not open untrusted X1, V8, or V9 files until the patch is applied.

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
TellusApplication
Affected:<= 4.0.17.0
Tellus LiteApplication
Affected:<= 4.0.17.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Fujielectric Tellus product
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Select-Object Name,Version to list installed software. Look for 'Fujielectric Tellus' or 'Fujielectric Tellus Lite'.
    Affected if Either Tellus or Tellus Lite appears in the installed programs list.
  2. Determine the installed version number
    Right-click the Tellus shortcut and select Properties, then check the 'Version' tab, or open the application and navigate to Help > About Tellus. Record the full version number displayed.
    Affected if The version is 4.0.17.0 or lower (e.g., 4.0.17.0, 4.0.16.0, 4.0.15.0, etc.).
  3. Verify file type support exists
    Open Tellus and attempt to access the file open dialog. Look for X1, V8, or V9 file extensions in the supported file type dropdown, or check the application documentation for supported file formats.
    Affected if The application supports opening or parsing X1, V8, or V9 file types.
  4. Check for recent file import activity
    Review the application log files (typically in the Tellus installation directory under 'Logs' or 'Log' folder) or check recent Windows file access events for X1, V8, or V9 files opened by the Tellus process.
    Affected if The software has recently parsed or attempted to parse X1, V8, or V9 files.

You are affected if Fujielectric Tellus or Tellus Lite is installed with version 4.0.17.0 or earlier and the application supports parsing X1, V8, or V9 file types.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 4.0.17.0
Interim mitigation

Update to a version newer than V4.0.17.0 when released by the vendor. Do not open untrusted X1, V8, or V9 files until the patch is applied.

Recommended fix Moderate confidence

Tellus V4.0.18.0 or later | Tellus Lite V4.0.18.0 or later (verify exact version from vendor)

  1. Locate and download the fixed version of Tellus or Tellus Lite from the official vendor website (hakko-elec.co.jp, monitouch.fujielectric.com, or as listed in the JVN advisory jvn.jp)
  2. Uninstall the current version of Tellus or Tellus Lite
  3. Install the updated version that addresses CVE-2023-47580
  4. Restart any running instances of the application
  5. Verify the version number reflects the patched release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tellus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47580 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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