LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0562: BlackIce Defender 2.1 and earlier, and BlackIce Pro 2.0.23 and earlier, do not properly block Back Orifice...

BlackIce Defender 2.1 and earlier, and BlackIce Pro 2.0.23 and earlier, do not properly block Back Orifice traffic when the security setting is Nervous or lower.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

BlackIce Defender 2.1 and BlackIce Pro 2.0.23 (and earlier) personal firewalls did not reliably block Back Orifice remote-access trojan traffic when the security level was set to "Nervous" or lower. Customers who relied on default or relaxed settings could have been silently backdoored despite believing the firewall was protecting them. This is a legacy 2000-era issue affecting long end-of-life products. Effectively none in modern environments. Network ICE was acquired by ISS (later IBM) and the BlackIce product line has been discontinued for well over a decade. Any surviving install would be on an unsupported Windows 9x/NT/2000-era host and is a much bigger operational problem than this specific filtering gap. Very low priority. This is a 2000-era defect in a discontinued personal firewall. Treat any discovery of BlackIce in the environment as an asset-lifecycle problem (unsupported software on legacy Windows) rather than a CVE to patch. No active exploitation is cited, and modern endpoint controls supersede the affected product entirely. Mitigation focus: Retire any remaining BlackIce Defender or BlackIce Pro installations; the product is end-of-life and unsupported.; If a legacy host still runs it, raise the BlackIce protection level above 'Nervous' per historical vendor guidance.; Replace with a currently supported endpoint protection and host firewall stack..

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-0562 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
1Source 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.