Hello team,
We are conducting an analysis of the events recorded by Azure Application Gateway WAF on our Confluence instance, with the aim of identifying potentially vulnerable behavior, anomalous requests, or false positives associated with native functionality, installed applications, and integrations.
During the analysis of the last 60 days, we identified detections associated with the following rules:
1. WAF Rule 942300 – Detection of patterns associated with SQL injection
Endpoints involved:
/confluence/rest/api/search/confluence/rest/quicknav/1/search
The events contain CQL search parameters with expressions such as #{portalunicoController.portalunico.opcionActual.tipo}.
We would appreciate your review of the following points:
- Whether these expressions and parameters correspond to legitimate Confluence behavior.
- Whether any integration or customization is generating these expressions.
- Whether processing these parameters could pose any risk of injection or query manipulation.
- Whether any applicable fixes, updates, or configuration recommendations are available.
2. WAF Rule 942350 – Detection of patterns associated with database structure or function manipulation
Endpoints involved:
/confluence/pages/diffpagesbyversion.action/confluence/login.action
The events show matches related to the selectedPageVersions parameter, which is used in the context of page version comparisons and authentication return parameters (os_destination).
We would appreciate your confirmation of the following:
- Whether the use of these parameters is consistent with expected Confluence behavior.
- Whether processing them involves any security risks.
- Whether this is a known WAF false positive triggered by native Confluence functionality.
- Whether any updates or recommended mitigations are available.
3. General security review
Additionally, we would appreciate it if you could review the following:
- Whether the installed Confluence version has any known vulnerabilities related to the behaviors described above.
- Whether the REST API, CQL, Quick Navigation, page version comparison, and authentication functionalities have any pending security updates or fixes.
- Whether any installed third-party applications could be involved in generating the identified requests.
- Whether there are any official recommendations for adjusting the WAF without reducing protection against actual attacks.
Our goal is to determine whether any behavior in Confluence needs to be corrected, whether any components need to be updated, or whether a specific and properly justified WAF exception should be maintained.
We can provide the original WAF events, including timestamps, source IP addresses, URIs, triggered rules, detection messages, and the data that caused the matches.
Thank you for your analysis and recommendations.
Best regards,