CVE-2020-25719
No exploitation reported by the sources we read.
- Published2022-02-18
- WeaknessCWE-287 · CWE-362
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A flaw was found in the way Samba, as an Active Directory Domain Controller, implemented Kerberos name-based authentication. The Samba AD DC, could become confused about the user a ticket represents if it did not strictly require a Kerberos PAC and always use the SIDs found within. The result could include total domain compromise.
Timeline
dates in UTC- 2022-02-1818:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-25719?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-25719?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 20.4 | = 20.04 | no fix published | NVD |
| 21.4 | = 21.04 | no fix published | NVD |
| 21.10 | = 21.10 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 33.x | = 33 | no fix published | NVD |
| 34.x | = 34 | no fix published | NVD |
| 35.x | = 35 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.15 | ≥ 4.15.0, < 4.15.2 | 4.15.2 | NVD |
| 4.14 | ≥ 4.14.0, < 4.14.10 | 4.14.10 | NVD |
| 4.x | ≥ 4.0.0, < 4.13.14 | 4.13.14 | NVD |
14 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- bind-dyndb-ldapAlmaLinux:8all versions · fixed in 11.6-2.module_el8.5.0+2603+92118e57
- custodiaAlmaLinux:8all versions · fixed in 0.6.0-3.module_el8.5.0+2603+92118e57and 1 other package
- custodiaAlmaLinux:8all versions · fixed in 0.6.0-3.module_el8.6.0+2881+2f24dc92and 1 other package
- ipa-clientAlmaLinux:8all versions · fixed in 4.9.6-10.module_el8.5.0+2603+92118e57and 14 other packages
- ipa-healthcheckAlmaLinux:8all versions · fixed in 0.7-6.module_el8.5.0+2603+92118e57and 1 other package
- opendnssecAlmaLinux:8all versions · fixed in 2.1.7-1.module_el8.5.0+2603+92118e57
- opendnssecAlmaLinux:8all versions · fixed in 2.1.7-1.module_el8.6.0+2881+2f24dc92
- python3-jwcryptoAlmaLinux:8all versions · fixed in 0.5.0-1.module_el8.5.0+2603+92118e57
17 more package ranges on OSV.dev
Fix
Advisories and patches
- bugzilla.redhat.comPatch
- www.samba.orgMitigation · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Published
- 2022-02-18
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-25719?
Is CVE-2020-25719 actively exploited?
What is the CVSS score for CVE-2020-25719?
Running ipa-client? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.