CVE-2014-3607: DefaultHostnameVerifier in Ldaptive (formerly vt-ldap) does not properly verify that the server hostname match

Q: How do I fix CVE-2014-3607?

ldaptive: upgrade to 1.0.5; vt-ldap: upgrade to 3.3.8. Exact commands for each OS are on this page.

Q: Is CVE-2014-3607 being exploited?

CVE-2014-3607 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2014-3607 affect?

CVE-2014-3607 affects ldaptive, vt-ldap. Severity is medium (CVSS 5.9). DefaultHostnameVerifier in Ldaptive (formerly vt-ldap) does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) field of the X.509 certificate, which allows man-in-the-middle attackers to spo

Q: How urgent is CVE-2014-3607?

Priority 40/100. Remotely exploitable, no login, no user action

This month

MEDIUM 5.9REMOTEUPGRADEUPGRADE

CVE-2014-3607 is a medium-severity flaw (CVSS 5.9) affecting ldaptive, vt-ldap. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

DefaultHostnameVerifier in Ldaptive (formerly vt-ldap) does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-295
Published	2018-01-08
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: ldaptive

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-01-08 19:29 UTCPublished CVE record published
2026-06-17 00:08 UTCUpdated Record last modified

ldaptive ldaptive UPGRADE

Affected: < 1.0.5

Fixed in: 1.0.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ldaptive || rpm -q ldaptive || ldaptive --version

2. UPGRADE to 1.0.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ldaptive

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ldaptive

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

ldaptive vt-ldap UPGRADE

Affected: < 3.3.8

Fixed in: 3.3.8

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vt-ldap || rpm -q vt-ldap || vt-ldap --version

2. UPGRADE to 3.3.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vt-ldap

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vt-ldap

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2014-3607?

ldaptive: upgrade to 1.0.5; vt-ldap: upgrade to 3.3.8. Exact commands for each OS are on this page.

Is CVE-2014-3607 being exploited?

CVE-2014-3607 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2014-3607 affect?

CVE-2014-3607 affects ldaptive, vt-ldap. Severity is medium (CVSS 5.9). DefaultHostnameVerifier in Ldaptive (formerly vt-ldap) does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) field of the X.509 certificate, which allows man-in-the-middle attackers to spo

How urgent is CVE-2014-3607?

Priority 40/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs