LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0532: A FreeBSD patch for SSH on 2000-01-14 configures ssh to listen on port 722 as well as port 22, which might...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A January 2000 FreeBSD patch for SSH inadvertently configured the service to also listen on TCP port 722 in addition to the standard port 22. If firewall rules only blocked port 22, remote users could still reach SSH through the alternate port. This is a legacy misconfiguration issue affecting FreeBSD systems from that era, not a modern vulnerability that impacts current infrastructure. Extremely limited today. Only FreeBSD hosts that installed the January 2000 SSH patch and never updated their base system or firewall rulesets remain exposed. No modern supported FreeBSD release ships this configuration. Any organization still running such a host has far larger operational risk than this specific issue. Very low priority for any modern environment. Treat as legacy hygiene: worth a quick check on any long-lived FreeBSD systems, but no incident response posture is warranted. Prioritize decommissioning or upgrading any host old enough to still carry this configuration. Mitigation focus: Upgrade FreeBSD to a currently supported release with a modern OpenSSH build.; Review sshd_config and remove any legacy ListenAddress or Port 722 entries.; Update firewall rules to filter all SSH ports, not only TCP/22..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2000-0532 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.