Skip to content
Fencer Vulns
medium 4.3

CVE-2021-33709 json

A vulnerability has been identified in Teamcenter Active Workspace V4 (All versions < V4.3.9), Teamcenter Active Workspace V5.0 (All versio…

published 2021-07-13 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-20386

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

A vulnerability has been identified in Teamcenter Active Workspace V4 (All versions < V4.3.9), Teamcenter Active Workspace V5.0 (All versions < V5.0.7), Teamcenter Active Workspace V5.1 (All versions < V5.1.4). By sending malformed requests, a remote attacker could leak an application token due to an error not properly handled by the system.

Patch / fix

  • siemens teamcenter_active_workspace 4.3.9, 5.0.7, 5.1.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-21-194-11 updated cvss 4.3

Siemens Teamcenter Active Workspace

  • Siemens Teamcenter Active Workspace V4 <V4.3.9
    affected: fixed in V4.3.9, mitigation
  • Siemens Teamcenter Active Workspace V5.0 <V5.0.7
    affected: fixed in V5.0.7, mitigation
  • Siemens Teamcenter Active Workspace V5.1 <V5.1.4
    affected: fixed in V5.1.4, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

  • Siemens Teamcenter Active Workspace V4
  • Siemens Teamcenter Active Workspace V5.0
  • Siemens Teamcenter Active Workspace V5.1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.