CVE-2000-0116: Firewall-1 does not properly filter script tags, which allows remote attackers to bypass the "Strip Script...

Security readout for executives and security teams

Check Point Firewall-1's content filter was supposed to strip out embedded web script tags to protect internal users from malicious pages, but attackers could sneak scripts past it by adding an extra "<" character in front of the SCRIPT tag. This meant the firewall's advertised "Strip Script Tags" protection could be bypassed, exposing users to hostile scripts the product was expected to block. Exposure is limited to legacy Check Point Firewall-1 deployments from circa 2000 relying on the "Strip Script Tags" HTTP content filter. Modern environments do not use this control, and the sources do not list specific affected versions or CPEs. Any organization still running that era's Firewall-1 in production would have far larger unsupported-software risks than this single filter bypass. Very low priority for modern environments. This is a 2000-era filter-bypass in a long-obsolete Check Point Firewall-1 feature, with no KEV listing and no cited active exploitation. It only matters if legacy Firewall-1 gear is still deployed, in which case the broader concern is unsupported infrastructure, not this single CVE. Mitigation focus: Confirm whether any legacy Check Point Firewall-1 instances remain in use and consult current Check Point guidance for supported successors.; Do not rely on the legacy 'Strip Script Tags' option as a browser protection; layer modern web filtering and endpoint controls instead.; Retire or upgrade unsupported Firewall-1 platforms as part of standard end-of-life hygiene..

Prepared

Jul 12, 2026, 01:14 UTC (UTC+00:00)

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