Make OWASP daily dependency scan resilient to NVD timeouts#1154
Merged
Conversation
…mits The NVD API v2 is extremely slow and unstable, especially when performing a full sync (cold start). This frequently triggers HTTP 524 Cloudflare timeouts. This change: - Dynamically handles NVD_API_KEY, avoiding passing an empty API key flag that could cause rate-limit penalties. - Increases connection and read timeouts to 120 seconds to tolerate NVD API slowness. - Increases the maximum NVD API request retry count to 20 to handle transient network errors.
Code Coverage Report
|
sayuzbas-google
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The daily security scan workflow (
dumper_daily_vulnerability_OWASP_scan.yml) was failing due to HTTP 524 Cloudflare timeouts during the initial NVD vulnerability database synchronization. This is caused by severe instability and rate-limiting on the NVD API v2.This PR makes the NVD synchronization more resilient by:
--nvdApiKeyparameter if the secretNVD_API_KEYis actually configured (non-empty), avoiding empty-string auth issues.--connectiontimeout 120000and--readtimeout 120000(120 seconds) to tolerate NVD API sluggishness.--nvdMaxRetryCount 20to allow the runner to recover from transient Cloudflare timeout spikes.Once the initial sync succeeds, subsequent runs will use the cached database and only download daily incremental updates, making them extremely fast and reliable.