CVE-2000-0532
First published: Wed Jun 07 2000(Updated: )
A FreeBSD patch for SSH on 2000-01-14 configures ssh to listen on port 722 as well as port 22, which might allow remote attackers to access SSH through port 722 even if port 22 is otherwise filtered.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| FreeBSD Kernel | =4.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2000-0532?
CVE-2000-0532 is considered a moderate severity vulnerability due to the potential for unauthorized remote SSH access.
How do I fix CVE-2000-0532?
To fix CVE-2000-0532, you should configure your SSH service to only listen on the default port 22 and ensure that port 722 is not exposed.
What systems are affected by CVE-2000-0532?
CVE-2000-0532 affects FreeBSD version 4.0, particularly with the SSH configuration allowing listening on port 722.
Can CVE-2000-0532 be exploited remotely?
Yes, CVE-2000-0532 can be exploited remotely by attackers attempting to access SSH through the unfiltered port 722.
What configurations should I check for CVE-2000-0532?
For CVE-2000-0532, check your SSHD configuration files to ensure that only port 22 is enabled and port 722 is disabled.
- agent/references
- agent/type
- agent/remedy
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-historical
- vendor/freebsd
- agent/software-canonical-lookup-request
- collector/nvd-index
- canonical/freebsd kernel
- version/freebsd kernel/4.0