Closed serpaldom closed 1 year ago
Hi and thanks for your contribution.
Will look into this a bit more and report back.
Regards.
I've checked the posts and improved the rule a little bit by including the vuln parameter and fixed the fields. Such rule would be best described in correlation as the attack requires multiple requests to those endpoint. I will push the rule later in a PR
title: Potential CVE-2023-27997 Exploitation Indicators
id: 31e4e649-7394-4fd2-9ae7-dbc61eebb550
status: experimental
description: |
Detects indicators of potential exploitation of CVE-2023-27997 in Frotigate weblogs.
To avoid false positives it's best to look for successive requests to the endpoints mentioned as well as weird values of the "enc" parameter
references:
- https://blog.lexfo.fr/Forensics-xortigate-notice.html
- https://blog.lexfo.fr/xortigate-cve-2023-27997.html
- https://research.kudelskisecurity.com/2023/06/12/cve-2023-27997-fortigate-ssl-vpn/
- https://labs.watchtowr.com/xortigate-or-cve-2023-27997/
author: Sergio Palacios Dominguez, Nasreddine Bencherchali (Nextron Systems)
date: 2023/07/28
tags:
- cve.2023.27997
logsource:
category: webserver
detection:
selection_uri:
cs-method:
- 'GET'
- 'POST'
cs-uri-query|contains:
- '/remote/hostcheck_validate'
- '/remote/logincheck'
selection_keywords:
- 'enc='
condition: all of selection_*
falsepositives:
- Unknown
level: medium
Description of the Idea of the Rule
Based on the vulnerability analysis reports for CVE-2023-27997 (CWE-122) , I would like to propose a detection rule for HTTP requests made to endpoints affected by the vulnerability, which could be a possible indication of being under attack.
Public References
Proposed rule