Silent failure in http_cors.yaml due to unvalidated regex logic

Summary

There is a "silent failure" where the http_cors.yaml module fails to detect vulnerabilities due to an incorrect regex pattern with a trailing space. Currently, the test suite (tests/test_yaml_regexes.py) only checks if a regex is syntactically valid, not if it actually matches the expected data.

As a result, http_cors.yaml passes all tests despite being logically broken for real-world scanning.

Description

In nettacker/modules/vuln/http_cors.yaml, the regex (http|https):\\/\\/evil.com contains a trailing space.
https://github.com/OWASP/Nettacker/blob/2310a8398f788bf7c3b767a153da151ab2a49445/nettacker/modules/vuln/http_cors.yaml#L336-L337

• Expected behavior: Match https://evil.com
• Actual behavior: Fails to match because servers do not append a space to the Access-Control-Allow-Origin header.

Testing gap: The current tests/test_yaml_regexes.py sees this as a valid regex string and passes it, even though it will never trigger a "Detected" status in a real scan.

Start with nettacker/modules/vuln/http_cors.yaml at the referenced regex and inspect tests/test_yaml_regexes.py to understand the current validation. Update the behavior so the expected https://evil.com value is matched, and extend the test coverage beyond syntax validity to verify matching data produces the expected detection result.