Skip to content

Commit

Permalink
fix: check valid for hours for NVD API (#6225)
Browse files Browse the repository at this point in the history
  • Loading branch information
jeremylong authored Dec 6, 2023
1 parent 4c44019 commit 38fd0af
Showing 1 changed file with 10 additions and 5 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -264,11 +264,16 @@ private void processDownload(Future<Future<NvdApiProcessor>> future, final Set<F

private boolean processApi() throws UpdateException {
final ZonedDateTime lastChecked = dbProperties.getTimestamp(DatabaseProperties.NVD_API_LAST_CHECKED);
if (cveDb.dataExists() && lastChecked != null) {
final ZonedDateTime thirtyMinutesAgo = ZonedDateTime.now().minusMinutes(30);
if (thirtyMinutesAgo.isBefore(lastChecked)) {
LOGGER.info("Skipping the NVD API Update as it was completed within the last 30 minutes");
return true;
final int validForHours = settings.getInt(Settings.KEYS.NVD_API_VALID_FOR_HOURS, 0);
if (cveDb.dataExists() && lastChecked != null && validForHours>0) {
// ms Valid = valid (hours) x 60 min/hour x 60 sec/min x 1000 ms/sec
final long validForSeconds = validForHours * 60L * 60L;
final ZonedDateTime now = ZonedDateTime.now(ZoneId.of("UTC"));
final Duration duration = Duration.between(lastChecked, now);
final long difference = duration.getSeconds();
if (difference < validForSeconds) {
LOGGER.info("Skipping the NVD API Update as it was completed within the last {} minutes", validForSeconds/60);
return false;
}
}

Expand Down

0 comments on commit 38fd0af

Please sign in to comment.