Summary of Changes:
Introduced enhancements to GitLab DAST parser, adding new method to process request/response details and a corresponding unit test to validate parsing functionality.

Security Findings:

1. Potential Information Exposure (dojo/tools/gitlab_dast/parser.py):

   • Direct inclusion of full request and response headers could expose sensitive information
   • No sanitization of header values
   • Risk of revealing authentication tokens or internal system details

2. Sensitive Information in Test Fixture (unittests/scans/gitlab_dast/issue_12050.json):

   • Contains partially masked credit card number
   • Exposed HTTP (non-secure) API endpoint
   • Includes masked Authorization header
   • High severity PII disclosure (CWE-359)
   • CVE: 10062

3. Network Security Concerns:

   • Exposed internal hostname "api-server"
   • Uses unsecured HTTP protocol
   • Potential authentication token exposure

4. Header Processing Risks:

   • No explicit sanitization of header names or values
   • Potential string formatting vulnerabilities
   • Minimal error handling for malformed evidence

5. Information Disclosure Risks:

   • Full request/response details stored without filtering
   • Potential exposure of sensitive system metadata
   • User agent and timestamp information included