LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » Legacy Products » Web Filter (R3000) » INFO: What is HTTP Packet Splitting Detection setting and what...

INFO: What is HTTP Packet Splitting Detection setting and what does it do?

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • R3000

Question:

What is HTTP Packet Splitting Detection setting and what does it do?

Reply

HTTP Packet Splitting Detection functionality is introduced in software version 2.0.12.10 to address a vulnerability that allows a user to break up HTTP requests across many small tcp packets.  Packet splitting is usually accomplished using a third party application.  When enabled, this option will allow you to configure the size of the packet for R3000 to detect (default is 48 bytes). With this option enabled, if R3000 detects a packet size equal or smaller than the specified size and the packet is an HTTP 1.1 request that contains a GET but no HOST header or vice versa, then request will be blocked as MALCOD or Malicious Code.

You can configure the packet size to as low as 5 bytes but please be aware that this may cause some over-blocking, so it is not recommended that this option be left 'on' or enabled by default but instead this is to be used in a specific case scenario where splitting is indeed taking place.  The smaller the packet size is configured, the higher the chance of over-blocking.
This article was previously published as:
8e6 KB 281966

To contact LevelBlue about this article or to request support:

Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster.


Execution: 0.078. 8 queries. Compression Disabled.
Powered by InstantKB.NET