CVE-2022-24290
No exploitation reported by the sources we read.
- Published2022-05-20
- Fixed in13.3.0.3 · 13.2.0.8 · 13.1.0.9 · 13.0.0.9 · 12.4.0.13
- WeaknessCWE-121 · CWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A vulnerability has been identified in Teamcenter V12.4 (All versions < V12.4.0.13), Teamcenter V13.0 (All versions < V13.0.0.9), Teamcenter V13.1 (All versions), Teamcenter V13.2 (All versions < V13.2.0.8), Teamcenter V13.3 (All versions < V13.3.0.3), Teamcenter V14.0 (All versions < V14.0.0.2). The tcserver.exe binary in affected applications is vulnerable to a stack overflow condition during the parsing of user input that may lead the binary to crash.
Timeline
dates in UTC- 2022-05-2013:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-24290?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-24290?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 13.3 | ≥ 13.3, < 13.3.0.3 | 13.3.0.3 | NVD |
| 13.2 | ≥ 13.2, < 13.2.0.8 | 13.2.0.8 | NVD |
| 13.1 | ≥ 13.1, < 13.1.0.9 | 13.1.0.9 | NVD |
| 13.0 | ≥ 13.0, < 13.0.0.9 | 13.0.0.9 | NVD |
| 12.4 | ≥ 12.4, < 12.4.0.13 | 12.4.0.13 | NVD |
| 14.0 | = 14.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Siemens Teamcenter
Teamcenter V12.4 · Teamcenter V13.0 · Teamcenter V13.1 · +3 more
Fix
- Update Siemens teamcenter to 13.3.0.3 · 13.2.0.8 · 13.1.0.9 · 13.0.0.9 · 12.4.0.13
- Vendor fix CISA ICSA-22-132-16 · 1 productUpdate to V12.4.0.13 or later version
- Vendor fix CISA ICSA-22-132-16 · 1 productUpdate to V13.0.0.9 or later version
- Vendor fix CISA ICSA-22-132-16 · 1 productUpdate to V13.1.0.9 or later version
- Vendor fix CISA ICSA-22-132-16 · 1 productUpdate to V13.2.0.8 or later version
- Vendor fix CISA ICSA-22-132-16 · 1 productUpdate to V13.3.0.3 or later version
- Vendor fix CISA ICSA-22-132-16 · 1 productUpdate to V14.0.0.2 or later version
Advisories and patches
- cert-portal.siemens.comMitigation · Patch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- CNAweakness (CWE)CWE-121read 2026-10-23
- NVDweakness (CWE)CWE-787read 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2022-05-20
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-24290?
Is CVE-2022-24290 actively exploited?
What is the CVSS score for CVE-2022-24290?
Running Siemens Teamcenter? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.