Skip to content
Fencer Intel
medium 5.9

CVE-2019-16546 json

Jenkins Google Compute Engine Plugin does not verify SSH host keys when connecting agents created by the plugin

published 6y ago modified 4mo ago also GHSA-345p-pw5q-g98v , EUVD-2022-2102

cvss
5.9
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

Jenkins Google Compute Engine Plugin 4.1.1 and earlier does not verify SSH host keys when connecting agents created by the plugin, enabling man-in-the-middle attacks.

Patch / fix

  • maven org.jenkins-ci.plugins:google-compute-engine 4.2.0
  • jenkins google_compute_engine 4.2.0

Is CVE-2019-16546 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.0 6.8 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:google-compute-engine
<4.2.0
4.2.0

Affected products

  • Jenkins project Jenkins Google Compute Engine Plugin

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key
  • CWE-300 Channel Accessible by Non-Endpoint

References

Sources

Fencer Intel 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.