Skip to content
Fencer Intel
high 8.1

CVE-2020-36658 json

In Apache::Session::LDAP before 0.5, validity of the X.509 certificate is not checked by default when connecting to remote LDAP backends, b…

published 3y ago modified 4mo ago also EUVD-2020-24104

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

In Apache::Session::LDAP before 0.5, validity of the X.509 certificate is not checked by default when connecting to remote LDAP backends, because the default configuration of the Net::LDAPS module for Perl is used. NOTE: this can, for example, be fixed in conjunction with the CVE-2020-16093 fix.

Patch / fix

  • lemonldap-ng apache::session::ldap 0.5
  • libapache-session-ldap-perl Debian 14, Debian 13, Debian 12 0.5-1

debian advisories DEBIAN-CVE-2020-36658

  • libapache-session-ldap-perl Ubuntu 20.04 LTS 0.4-1+deb10u1build0.20.04.1
  • libapache-session-ldap-perl Ubuntu Pro 16.04 LTS 0.4-1ubuntu0.16.04.1~esm1
  • libapache-session-ldap-perl Ubuntu Pro 18.04 LTS 0.4-1ubuntu0.18.04.1~esm1

ubuntu advisories UBUNTU-CVE-2020-36658

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-36658 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

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

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness
  • CWE-295 Improper Certificate Validation

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.