SEC_PROTOCOL_ERROR_FURTHER_ACTION and Bad Packets
Last updated on JUNE 05, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
Oracle documentation simply states that "SEC_PROTOCOL_ERROR_FURTHER_ACTION specifies the further execution of a server process when receiving bad packets from a possibly malicious client."
The documentation on this parameter is not very detailed and leaves some questions.
1. What is considered a "Bad Packet"? Malformed packet? Bad header, bad content, other?
2. Does a "malicious client" mean that the attack is always human-generated, or can a faulty NIC or application cause bad packets?
3. How can one simulate a series of bad packets against the database to generate trace and alert entries so we can identify when this issue happens?
4. Is there any performance overhead to setting this parameter?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms