What is CVE-2023-38076?A high-severity flaw in Jt2go, explained.
CVE-2023-38076 is a high-severity flaw (CVSS 7.8) in Jt2go from Siemens, published on 12 September 2023. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.4%. If you run an affected version, plan in the vendor’s fix.
Published 12 September 2023. Record last updated 16 February 2024. We keep this page's data up to date.
What is CVE-2023-38076? In plain terms.
An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.
A vulnerability has been identified in JT2Go (All versions < V14.3.0.1), Teamcenter Visualization V13.3 (All versions < V13.3.0.12), Teamcenter Visualization V14.0 (All versions), Teamcenter Visualization V14.1 (All versions < V14.1.0.11), Teamcenter Visualization V14.2 (All versions < V14.2.0.6), Teamcenter Visualization V14.3 (All versions < V14.3.0.1), Tecnomatix Plant Simulation V2201 (All versions < V2201.0010), Tecnomatix Plant Simulation V2302 (All versions < V2302.0004). The affected application is vulnerable to heap-based buffer overflow while parsing specially crafted WRL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21041)
What kind of flaw is it?
- CWE-787Out-of-bounds Write
- CWE-122Heap-based Buffer Overflow
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickYes, a person has to take an action
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is CVE-2023-38076 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2023-38076 scores 46. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2023-38076 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2023-38076? 3 products.
The published record lists 3 products from 1 vendor. Versions are shown as published: "before 14.3.0.1" means every version up to, but not including, 14.3.0.1. If you run one of these, check your version, then go to the fix below.
- Application
Jt2go
by Siemens
Affected versionsbefore 14.3.0.1 - Application
Teamcenter Visualization
by Siemens
Affected versions13.3.0 to before 13.4.0.1214.0 to before 14.1.0.1114.2 to before 14.2.0.614.3 to before 14.3.0.1 - Application
Tecnomatix Plant Simulation
by Siemens
Affected versions2201.0 to before 2201.00102302.0 to before 2302.0004
How do I fix CVE-2023-38076? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2023-38076 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A vulnerability has been identified in JT2Go (All versions < V14.3.0.1), Teamcenter Visualization V13.3 (All versions < V13.3.0.12), Teamcenter Visualization...
- Matched to
- Jt2go on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2023-38076 is a high-severity flaw in Jt2go from Siemens, published on 12 September 2023. An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.
It scores 7.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2023-38076 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.4%. That can change at any time, which is why we keep watching.
For Jt2go from Siemens: before 14.3.0.1. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.