Skip to content
Fencer Vulns
medium 5.3

CVE-2020-7042 json

An issue was discovered in openfortivpn 1.11.0 when used with OpenSSL 1.0.2 or later.

published 2020-02-27 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-28176

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

Summary

An issue was discovered in openfortivpn 1.11.0 when used with OpenSSL 1.0.2 or later. tunnel.c mishandles certificate validation because the hostname check operates on uninitialized memory. The outcome is that a valid certificate is never accepted (only a malformed certificate may be accepted).

Patch / fix

  • openfortivpn_project openfortivpn 1.12.0
  • openfortivpn Debian 14, Debian 13, Debian 12 1.12.0-1

debian advisories DEBIAN-CVE-2020-7042

  • openfortivpn openSUSE Tumbleweed 1.17.1-1.1
  • openfortivpn Package Hub 15 SP1 1.12.0-bp151.3.3.1
  • openfortivpn openSUSE Leap 15.1 1.12.0-lp151.2.5.1

opensuse advisories openSUSE-SU-2024:11118-1openSUSE-SU-2020:0305-1openSUSE-SU-2020:0301-1

Vendor advisories

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

red hat product security vex CVE-2020-7042 updated cvss 5.3

openfortivpn: mishandling of certificate validation due to an uninitialized memory

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

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

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-908 Use of Uninitialized Resource

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.