Improper signature verification of Printer driver installation in TeamViewer Remote Clients

Versions reported by the vendor

Affected version ranges reported by the assigning authority (TV). Independent of NVD's CPE analysis and usually ahead of it.

• TeamViewer Remote Full Client

  • 15.0.0 and later · before 15.58.4affected
  • 14.0.0 and later · before 14.7.48796affected
  • 13.0.0 and later · before 13.2.36225affected
  • 12.0.0 and later · before 12.0.259312affected
  • 11.0.0 and later · before 11.0.259311affected

• TeamViewer Remote Host

  • 15.0.0 and later · before 15.58.4affected
  • 14.0.0 and later · before 14.7.48796affected
  • 13.0.0 and later · before 13.2.36225affected
  • 12.0.0 and later · before 12.0.259312affected
  • 11.0.0 and later · before 11.0.259311affected

Other highest-scoring records for the same primary product.

• CVE-2024-7479Improper signature verification of VPN driver installation in TeamViewer Remote Clients
  35Monitor
• CVE-2025-0065Improper Neutralization of Argument Delimiters in TeamViewer Clients
  31Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const claims = jwt.verify(token, publicKey);

1const claims = jwt.verify(token, publicKey, {2  algorithms: ["RS256"],3  issuer: "https://id.example.com",4  audience: "portal",5});

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.