Skip to content

Update penetration test report for 10.4#25634

Merged
EngincanV merged 2 commits into
rel-10.4from
docs/update-penetration-report-10.4
Jun 15, 2026
Merged

Update penetration test report for 10.4#25634
EngincanV merged 2 commits into
rel-10.4from
docs/update-penetration-report-10.4

Conversation

@salihozkara

@salihozkara salihozkara commented Jun 15, 2026

Copy link
Copy Markdown
Member

Copilot AI review requested due to automatic review settings June 15, 2026 14:32
@github-actions

Copy link
Copy Markdown
Contributor

Images automagically compressed by Calibre's image-actions

Compression reduced images by 69.2%, saving 234.6 KB.

Filename Before After Improvement Visual comparison
docs/en/images/pen-test-alert-list-10.4.png 339.1 KB 104.5 KB 69.2% View diff

@salihozkara salihozkara requested a review from EngincanV June 15, 2026 14:34
@salihozkara salihozkara added this to the 10.4-patch milestone Jun 15, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the public OWASP ZAP penetration test report documentation to reflect ABP Commercial MVC v10.4.0, aligning the example findings and guidance with the latest scan results.

Changes:

  • Updates the report intro, affected URL examples, and several alert explanations to match the 10.4 ZAP scan.
  • Replaces the alert summary screenshot reference with the 10.4 image.
  • Rephrases some sections to better distinguish framework defaults vs application/deployment-specific security configuration.

@@ -74,37 +49,14 @@ SQL injection may be possible.

This is a **false-positive** alert. ABP Framework uses Entity Framework Core, which inherently uses parameterized queries, preventing standard SQL injection attacks. Manual verification showed that injecting SQL syntax into parameters like `providerKey` results in the input being treated as a literal string (resulting in no match or default behavior) rather than altering the query structure.
@@ -306,13 +243,12 @@ Manually confirm that the timestamp data is not sensitive, and that the data can

This vulnerability was reported as a positive alert, because ABP uses the [zxcvbn](https://github.com/dropbox/zxcvbn) library for [password complexity indicators](../framework/ui/angular/password-complexity-indicator-component.md). This library is one of the most used password strength estimator and it does not disclosure any sensitive data related to web server's timestamp and therefore it's a **false-positive** alert.
* *[GET] — https://localhost:44349 (and other several URLs...)*
* *[GET] — https://localhost:44349/Abp/Languages/Switch?culture=ar&returnUrl=%2F%3Fpage%3D% (same url with different query parameters...)*
* *[GET] — https://localhost:44348 (and other several URLs...)*
* *[GET] — https://localhost:44348/Abp/Languages/Switch?culture=ar&returnUrl=%2F%3Fpage%3D% (same url with different query parameters...)*
Comment on lines +26 to +28
- *[GET] - https://localhost:44348/api/audit-logging/audit-logs?httpMethod=audit-logs&sorting=executionTime+desc&skipCount=0&maxResultCount=10*
- *[GET] - https://localhost:44348/Account/ForgotPassword?returnUrl=%5CForgotPassword*
- *[GET] - https://localhost:44348/Account/Login?ReturnUrl=%2FAccount%2FManage*
Comment on lines 194 to +196
### Cookie without `SameSite` Attribute [Risk: Low] — Positive (No need for a fix)

* *[GET] — https://localhost:44349/Abp/Languages/Switch?culture=ar&returnUrl=%2F&uiCulture=ar _(and other several URLs with different query parameters...)_*
* *[GET] — https://localhost:44348/Abp/Languages/Switch?culture=ar&returnUrl=%2F&uiCulture=ar _(and other several URLs with different query parameters...)_*
@EngincanV EngincanV merged commit 389b995 into rel-10.4 Jun 15, 2026
1 check passed
@EngincanV EngincanV deleted the docs/update-penetration-report-10.4 branch June 15, 2026 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants