CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. Come to CPUG CON 2008 EUROPE in Switzerland on September 8th - 9th!
    Two days full of technical content for Check Point administrators in the beautiful Swiss Alps!
    We already have sign-ups from twelve different countries!
2. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 7/14, 8/25, 10/6, 11/3, 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3, 9/7.
3. Corrent S3500 SecureXL Turbocards For Sale - Last Six Remaining - Get Your Spares!
4. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > Content Security/Security Servers/CVP/UFP
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2007-01-02
bahuguna_praveen bahuguna_praveen is offline
Junior Member
 
Join Date: 2006-03-07
Posts: 10
Rep Power: 0
bahuguna_praveen has an average reputation (10+)
Default new line character check on firewall

Hi All,

I want to know what are the risk associated with disabling #FTP_ENFORCE_NL argument on checkpoint firewall. I know disabling this arugment will force CP to bypass newline character check.

Does any one know what is the risk of firewall not doing new line character check on FTP connection.

Thanks in advance

Rgds
Reply With Quote
  #2 (permalink)  
Old 2007-01-03
northlandboy northlandboy is offline
Senior Member
 
Join Date: 2006-07-28
Location: New Zealand
Posts: 747
Rep Power: 2
northlandboy has an average reputation (10+)
Default Re: new line character check on firewall

You'll probably need to read deeply into the RFCs to understand it all, but I guess there are some attacks that could be mounted. My reading of it is that if it's only for outbound FTP, then it's not such an issue.

If you're having this problem with specific FTP servers, then I would strongly recommend that you have a specific rule for those connections, above any other FTP rules, and use the FTP basic service. Create a new TCP service, called ftp-basic, or similar. Then set the advanced protocol type to FTP-BASIC.

This disables several security checks, including the newline one. The advantage of using it this way is that it then only applies to those connections, rather than all FTP rules, like changing base.def does. The other thing is that changes to base.def are not automatically upgraded, whereas using the ftp basic service will be carried across upgrades. Otherwise what tends to happen is that you forget about the change, then upgrade a year later, and things start breaking again.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -7. The time now is 20:15.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
LinkBacks Enabled by vBSEO 3.0.0