LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0779: Checkpoint Firewall-1 with the RSH/REXEC setting enabled allows remote attackers to bypass access restricti...

Checkpoint Firewall-1 with the RSH/REXEC setting enabled allows remote attackers to bypass access restrictions and connect to a RSH/REXEC client via malformed connection requests.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A very old Check Point Firewall-1 configuration issue let outside attackers reach internal RSH or REXEC clients by sending malformed connection requests when those legacy remote-shell services were enabled through the firewall. In plain terms, a security control that should have blocked risky remote-access traffic could be tricked into passing it through. Exposure is limited to environments still running late-1990s/early-2000s Check Point Firewall-1 versions with RSH/REXEC inspection enabled and legacy r-services reachable behind the firewall. Modern deployments have long since retired these code paths, so real-world exposure today should be minimal but non-zero in unmanaged legacy segments. Low priority for modern estates. This is a 25-year-old firewall configuration flaw; treat it as legacy hygiene rather than an urgent incident. Only elevate priority if inventory confirms Firewall-1 of that era is still in production or if legacy r-services remain reachable from untrusted networks. Mitigation focus: Follow the Check Point advisory referenced in the bundle and apply any vendor-supplied fix for Firewall-1 RSH/REXEC handling.; Disable RSH/REXEC inspection on Firewall-1 if the legacy r-services are not required in the environment.; Block or filter inbound RSH (TCP 514) and REXEC (TCP 512) at the perimeter and internal enforcement points..

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-0779 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.