← console
voxell vciy

CVE-2023-38683

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: teamcenter visualization 14.1.0.10; teamcenter visualization 14.2.0.5; jt2go 14.2.0.5 upper bounds of the CVE record's affected ranges
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

A vulnerability has been identified in JT2Go (All versions < V14.2.0.5), Teamcenter Visualization V13.2 (All versions < V13.2.0.14), Teamcenter Visualization V14.1 (All versions < V14.1.0.10), Teamcenter Visualization V14.2 (All versions < V14.2.0.5). The affected application contains an out of bounds write past the end of an allocated buffer while parsing a specially crafted TIFF file. This could allow an attacker to execute code in the context of the current process.

weakness
CWE-787: Out-of-bounds Write
affected
Siemens JT2Go; Siemens Teamcenter Visualization V13.2; Siemens Teamcenter Visualization V14.1; Siemens Teamcenter Visualization V14.2
published ranges
siemens jt2go < 14.2.0.5; siemens teamcenter visualization >= 14.1 < 14.1.0.10; siemens teamcenter visualization >= 14.2 < 14.2.0.5
first unaffected version, by branch
teamcenter visualization 14.1.0.10; teamcenter visualization 14.2.0.5; jt2go 14.2.0.5
severity
7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
assigned by
siemens
published
2023-08-08

check us cert-portal.siemens.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
9 Aug 20230.0005
15 Aug 20230.00066
17 Sep 20230.00053
21 Oct 20230.0005
17 Mar 20250.00053scoring model v2025.03.14
3 May 20260.00081
4 Jun 20260.00086
15 Jun 20260.00275scoring model v2026.06.15
9 Aug 20260.00311

18 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-08-09 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: teamcenter visualization 14.1.0.10; teamcenter visualization 14.2.0.5; jt2go 14.2.0.5. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2023-38683', '2026-10-31T23:59:59.999999Z', now());