Skip to content
Fencer Intel
low 3.4

CVE-2020-4640 json

Certain IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 configurations can result in sensitive information in…

published 5y ago modified 4mo ago also EUVD-2020-25887

cvss
3.4
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

Certain IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 configurations can result in sensitive information in the URL fragment identifiers. This information can be cached in the intermediate nodes like proxy servers, cdn, logging platforms, etc. An attacker can make use of this information to perform attacks by impersonating a user. IBM X-Force ID: 185510.

Is CVE-2020-4640 in your stack? 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.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 3.4 CVSS:3.0/PR:L/AC:H/UI:R/S:U/I:L/A:N/C:L/AV:A/RC:C/RL:O/E:U
NVD 3.1 4.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
CNA 3.0 3.4 CVSS:3.0/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
NVD 2.0 3.8 AV:A/AC:M/Au:S/C:P/I:P/A:N

Affected products

  • IBM API Connect

Classification

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

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.