-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New Rule] Potential Buffer Overflow Attack Detected #3312
Conversation
reference = "https://attack.mitre.org/tactics/TA0001/" | ||
|
||
[rule.threshold] | ||
field = ["event.kind"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may want to limit this somehow, by host.id
maybe? If not, this would be triggered by unrelated activities in different systems on the same env
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@w0rk3r I added the host.id field to the threshold, making it match on similar event.kind
and host.id
values.
For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html). | ||
- Click "Save and Continue". | ||
- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts. | ||
For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May require a few line additions post review from @approksiu
https://docs.google.com/document/d/1J4ClwoAkhcP4BDTw94Bwb3nC_6kXsl5pu99Um8Ddt58/edit?pli=1
We need to mention the dependent Detection rule that needs to be enabled for this threshold rule to fire.
@approksiu would you mind giving this setup guide a double check? |
rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml
Outdated
Show resolved
Hide resolved
rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml
Outdated
Show resolved
Hide resolved
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
* [New Rule] Potential Buffer Overflow Attack * Added timestamp_override * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml * Update rules/linux/privilege_escalation_potential_bufferoverflow_attack.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 48d8b65)
Summary
Detects potential buffer overflow attacks by querying the "Segfault Detected" pre-built rule signal index, through a
threshold rule, with a minimum number of 100 segfault alerts in a short timespan. A large amount of segfaults in a short
time interval could indicate application exploitation attempts.
Detection
This rule leverages the alert data from the "Segfault Detected" pre-built rule (https://github.com/elastic/detection-rules/blob/main/rules_building_block/execution_linux_segfault.toml).