ZAP JavaScript Engine Memory Leak Issue Impacts Active Scan Usage
## Cybersecurity: ZAP JavaScript Engine Memory Leak Disclosed
Cybersecurity: ZAP JavaScript Engine Memory Leak Disclosed
The Zed Attack Proxy (ZAP) project, an open-source web application security scanner, has identified a memory leak in its JavaScript engine. This issue affects active scanning workflows following the addition of a new JavaScript scan rule in the OpenAPI add-on.
The memory leak causes potential denial-of-service-like conditions for security teams using ZAP for dynamic application security testing (DAST). The problem arises during active scans, where the JavaScript engine fails to deallocate resources properly, leading to rapid memory consumption. This vulnerability is linked to inefficient memory handling, possibly due to long-running script executions or unhandled garbage collection in scan rules.
Crashes or hangs in scanning sessions, disrupting vulnerability discovery. Increased resource usage on scanning hosts, potentially affecting broader infrastructure in CI/CD environments. Delayed security assessments for teams using ZAP in Docker or standalone deployments.
While the flaw does not expose scanned applications to exploits, it undermines ZAP's reliability as a security tool, delaying patch identification in production environments.
To mitigate risks, the OpenAPI add-on has been updated to disable the problematic JavaScript scan rule by default. Users are advised to update to the latest version to apply this workaround. ZAP's nightly and weekly releases now include the fix, along with updated Docker images for weekly and live channels.
The Zed Attack Proxy (ZAP) project, an open-source web application security scanner, has identified a memory leak in its JavaScript engine.
Release Type Status Update Advice
Nightly Updated Pull latest for testing
Weekly Updated Recommended for production scans
Docker (Weekly/Live) Updated Rebuild containers promptly
Stable Pending Monitor for underlying fix
Developers should verify installations using zaproxy --version and re-enable the rule only after a permanent fix is applied. ZAP maintainers are working on a permanent resolution to the memory leak, with ongoing updates expected. Security professionals should monitor ZAP's GitHub repository for announcements regarding stable releases.
Additionally, the ZAP team has introduced the OWASP PTK add-on , version 0.2.0 alpha, which integrates the OWASP Penetration Testing Kit browser extension into ZAP-launched browsers.
Based on reporting by Cyber Security News.
