nday

À propos de nday

nday représente le cycle de vie de chaque vulnérabilité sous forme de chronologie : divulgation, correctif, analyse technique, preuve de concept publique, exploitation active, inscription au catalogue KEV de la CISA. La page d’accueil liste les vulnérabilités qui viennent de franchir une nouvelle étape ; chaque page de vulnérabilité indique, pour chaque événement, sa source, la précision de sa date et les données brutes.

Le principe : ce qui n’est pas connu est présenté comme inconnu. Les événements sans date fournie par la source sont marqués « date inconnue » ; les étapes déduites (comme une exploitation déduite d’une inscription au KEV) ne reçoivent qu’une date au plus tard et indiquent sur quoi repose la déduction ; les données importées en masse ne se font jamais passer pour une observation en direct. Sources : ~/src.

Le site ne charge aucune ressource tierce.

This product uses data from the NVD but is not endorsed or certified by the NVD.

Contact : [email protected].

Comments on vulnerability pages follow these rules: Community rules

Ordering and pinning on the home page

The home list (~/) is ordered by when each vulnerability last reached a new stage, newest first. For each kind of lifecycle event nday takes its earliest known time, and the latest of those times places the vulnerability; on equal times the one at the higher current stage comes first.

Once a kind of event has a known time, further events of that kind, such as another advisory with a patch or another PoC, never move the vulnerability up again. Events whose time is unknown (the source gave none and nday did not observe them live) do not count as a change, and neither do posts to the oss-security mailing list.

By default the list covers the last 7d and only vulnerabilities whose latest change is to PAT or a later stage, so a newly published CVE alone does not appear; --since and --min-stage change this. CVE records marked REJECTED are left out unless --include-rejected is on.

On the first page, nday pins up to 10 vulnerabilities that researchers are discussing right now above the list. A vulnerability is pinned only when all of the following hold.

  • At least 2 different researchers on nday's list posted about it on X in the last 7d.
  • Its latest researcher post is from today or the 3 UTC days before.
  • Its current wave of discussion began today or in the 7 UTC days before. A wave is a run of posts on UTC days at most 7 days apart: a vulnerability discussed again after a longer silence can be pinned again, and one discussed without such a break stops being pinned 7 days after the day its wave began.
  • It would be in the list you are viewing anyway: same window, minimum stage, rejected switch and tags.

Pinned rows are ordered by the number of researchers, then by the latest post. If fewer qualify than the limit, the rest is filled from the top of the discussed ranking, whatever the window or minimum stage. Pinned rows appear only on the first page and are not repeated among the ordinary rows.

The numbers above are the settings in force now.

Raccourcis clavier

j / k
déplacer le curseur entre les lignes d’une liste ou entre les événements
Enter
ouvrir la vulnérabilité sous le curseur
/
placer le curseur dans le champ de recherche (Échap pour en sortir)
y
copier l’identifiant CVE
o
page de vulnérabilité : ouvrir la source de l’événement sous le curseur
u
revenir à la page précédente
?
afficher ou masquer l’aide des raccourcis

Les raccourcis sont désactivés pendant la saisie dans un champ et tant qu’une touche Ctrl, Alt ou ⌘ est maintenue enfoncée.