ID

VAR-200010-0031


CVE

CVE-2000-0779


TITLE

Checkpoint Firewall-1 Vulnerability

Trust: 0.6

sources: CNNVD: CNNVD-200010-094

DESCRIPTION

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. Check Point Firewall-1 is vulnerable to certain unauthorized connections, caused by sending a specially formatted RSH/REXEC connection request from an external RSH/REXEC server to an internal (protected) RSH/REXEC client. This can only be done if the FireWall-1 administrator specifically enabled RSH/REXEC with stderr-port support in the Properties window. The problem has to do with the pending table used to store state information for when rsh connections are initialized with stderr-port support. The pending table is a Firewall-1 internal memory structure used to hold temporary information about the state of a new connection before it is added to the "connection table", where state information (remote, destination ip addresses and ports, protocol type, etc) for permitted connections is stored. Because of the way data from the pending table is interpreted and certain conditions met by the nature of Firewall-1's handling of the rsh/rexec stderr-port (the acceptance of an additional syn packet), it is possible to collide an entry in the pending table before it is written to the connection table as the stderr-port connection. When stderr connections for rsh/rexec are permitted, information from the first data packet of an rsh connection is stored in the pending table so the firewall can anticipate the stderr syn. The stderr port is extracted from the tcp data segment of this initial data packet. In addition, the source, destination ip addresses and ports are stored, as well as a magic number and the IP protocol code. Firewall-1 then waits for a syn for the stderr connection. When one is recieved, another entry is made into the pending table, only the sequence number + 1 is stored in the place where the IP protocol number would go. If a malicious SYN is crafted with a sequence number of 5 and sent to the Firewall-1 that is expecting a rsh/rexec stderr syn, the sequence number will be stored as 6 in the place where the protocol code (which happened to be 6, for TCP) is for the previous entry. The firewall then checks this and allows this connection to be established regardless of what the port is in the malicious syn. It is then possible for an attacker to communicate with an "rsh client' on an arbitrary port behind the firewall. The impact is that if rsh/rexec stderr-port is permitted, back-connections through the firewall can be established. Checkpoint Firewall-1 with valid RSH/REXEC settings has a vulnerability

Trust: 1.26

sources: NVD: CVE-2000-0779 // BID: 1534 // VULHUB: VHN-2356

AFFECTED PRODUCTS

vendor:checkpointmodel:firewall-1scope:eqversion:4.0

Trust: 1.6

vendor:checkpointmodel:firewall-1scope:eqversion:3.0

Trust: 1.6

vendor:checkpointmodel:firewall-1scope:eqversion:4.1

Trust: 1.6

vendor:checkmodel:point software firewall-1scope:eqversion:4.1

Trust: 0.3

vendor:checkmodel:point software firewall-1scope:eqversion:4.0

Trust: 0.3

vendor:checkmodel:point software firewall-1scope:eqversion:3.0

Trust: 0.3

sources: BID: 1534 // CNNVD: CNNVD-200010-094 // NVD: CVE-2000-0779

CVSS

SEVERITY

CVSSV2

CVSSV3

nvd@nist.gov: CVE-2000-0779
value: HIGH

Trust: 1.0

CNNVD: CNNVD-200010-094
value: HIGH

Trust: 0.6

VULHUB: VHN-2356
value: HIGH

Trust: 0.1

nvd@nist.gov: CVE-2000-0779
severity: HIGH
baseScore: 7.5
vectorString: AV:N/AC:L/AU:N/C:P/I:P/A:P
accessVector: NETWORK
accessComplexity: LOW
authentication: NONE
confidentialityImpact: PARTIAL
integrityImpact: PARTIAL
availabilityImpact: PARTIAL
exploitabilityScore: 10.0
impactScore: 6.4
acInsufInfo: NONE
obtainAllPrivilege: NONE
obtainUserPrivilege: NONE
obtainOtherPrivilege: NONE
userInteractionRequired: NONE
version: 2.0

Trust: 1.0

VULHUB: VHN-2356
severity: HIGH
baseScore: 7.5
vectorString: AV:N/AC:L/AU:N/C:P/I:P/A:P
accessVector: NETWORK
accessComplexity: LOW
authentication: NONE
confidentialityImpact: PARTIAL
integrityImpact: PARTIAL
availabilityImpact: PARTIAL
exploitabilityScore: 10.0
impactScore: 6.4
acInsufInfo: NONE
obtainAllPrivilege: NONE
obtainUserPrivilege: NONE
obtainOtherPrivilege: NONE
userInteractionRequired: NONE
version: 2.0

Trust: 0.1

sources: VULHUB: VHN-2356 // CNNVD: CNNVD-200010-094 // NVD: CVE-2000-0779

PROBLEMTYPE DATA

problemtype:NVD-CWE-Other

Trust: 1.0

sources: NVD: CVE-2000-0779

THREAT TYPE

remote

Trust: 0.6

sources: CNNVD: CNNVD-200010-094

TYPE

unknown

Trust: 0.6

sources: CNNVD: CNNVD-200010-094

EXTERNAL IDS

db:BIDid:1534

Trust: 2.0

db:OSVDBid:1487

Trust: 1.7

db:NVDid:CVE-2000-0779

Trust: 1.7

db:CNNVDid:CNNVD-200010-094

Trust: 0.6

db:VULHUBid:VHN-2356

Trust: 0.1

sources: VULHUB: VHN-2356 // BID: 1534 // CNNVD: CNNVD-200010-094 // NVD: CVE-2000-0779

REFERENCES

url:http://www.securityfocus.com/bid/1534

Trust: 1.7

url:http://www.checkpoint.com/techsupport/alerts/list_vun.html#improper_stderr

Trust: 1.7

url:http://www.osvdb.org/1487

Trust: 1.7

url:http://www.monkey.org/~dugsong/talks/blackhat.pdf

Trust: 0.3

url:http://www.checkpoint.com/techsupport/alerts/list_vun.html

Trust: 0.3

sources: VULHUB: VHN-2356 // BID: 1534 // CNNVD: CNNVD-200010-094 // NVD: CVE-2000-0779

CREDITS

The following individuals discovered this vulnerability and discussed it at Black Hat 2000. Thomas Lopatic and John McDonald, TUV data protect GmbH Dug Song, University of Michigan CITI

Trust: 0.3

sources: BID: 1534

SOURCES

db:VULHUBid:VHN-2356
db:BIDid:1534
db:CNNVDid:CNNVD-200010-094
db:NVDid:CVE-2000-0779

LAST UPDATE DATE

2024-08-14T15:25:52.204000+00:00


SOURCES UPDATE DATE

db:VULHUBid:VHN-2356date:2008-09-10T00:00:00
db:BIDid:1534date:2000-08-02T00:00:00
db:CNNVDid:CNNVD-200010-094date:2006-01-04T00:00:00
db:NVDid:CVE-2000-0779date:2008-09-10T19:05:49.897

SOURCES RELEASE DATE

db:VULHUBid:VHN-2356date:2000-10-20T00:00:00
db:BIDid:1534date:2000-08-02T00:00:00
db:CNNVDid:CNNVD-200010-094date:2000-10-20T00:00:00
db:NVDid:CVE-2000-0779date:2000-10-20T04:00:00