🎉 Add fix_available to KrakenDAudit

[manuel-sommer]

#12633 (comment)

I removed also the mitigation from dedeuplication as this was only there to close the old finding in case the mitigation becomes available.

[dryrunsecurity]

This pull request contains a potential misinformation issue in the KrakenD audit report parser, where the code incorrectly hardcodes fix_available=True for all findings, which could mislead users about the actual remediation status of vulnerabilities.

Incorrect State Reporting / Misinformation in dojo/tools/krakend_audit/parser.py

Vulnerability	Incorrect State Reporting / Misinformation
Description	The code hardcodes fix_available=True for all findings parsed from KrakenD audit reports. This is problematic because it assumes a fix is always available, which is unlikely to be true for all security findings. This can mislead users about the true remediation status of vulnerabilities, potentially causing them to misprioritize remediation efforts or giving a false sense of security.

django-DefectDojo/dojo/tools/krakend_audit/parser.py

Lines 29 to 35 in 3cb19c7

	mitigation=message,
	static_finding=True,
	dynamic_finding=False,
	fix_available=True,
	)
	findings.append(finding)
	return findings

---

All finding details can be found in the DryRun Security Dashboard.

[mtesauro]

Approved