CVE-2000-0668 json
pam_console PAM module in Linux systems allows a user to access the system console and reboot the system when a display manager such as gdm…
published 2000-07-27 26 y ago modified 2026-06-16 4 mo ago also EUVD-2000-0664
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.2%
- EPSS 7.2% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
pam_console PAM module in Linux systems allows a user to access the system console and reboot the system when a display manager such as gdm or kdm has XDMCP enabled.
Patch / fix
- securityfocus.com/bid/1513 advisory
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-2000-0668 updated
security flaw
-
Red Hat All currently supported Red Hat productsnot 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
Timeline
- First public exploit (EDB-20105)
- Published
Exploit prediction
7.24% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-20105 Conectiva 4.x/5.x / RedHat 6.x - pam_console Remote User remote, 2000-07-27
- securityfocus.com http://www.securityfocus.com/bid/1513 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
References
-
securityfocus.com
/bid/1513
vdb-entry, exploit, patch, vendor-advisory
-
redhat.com
/support/errata/RHSA-2000-044.html
vendor-advisory
-
archives.neohapsis.com
/archives/bugtraq/2000-07/0455.html
mailing-list
-
archives.neohapsis.com
/archives/bugtraq/2000-07/0398.html
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/5001
vdb-entry
Sources
- CVE List CVE-2000-0668
- NVD CVE-2000-0668
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.