Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

16 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

One change, in full: Product added: 16 products named as affected in CVE-2023-3332. The same change in 1 CVE record, across 16 products: 16 rows in all. Back to all 16 products in this change · Back to the ledger

Counted changes published by NEC, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wf300hpTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wg1400hpTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wg1800hpTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wg1800hp2Time to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wg2600hpTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wg2600hp2Time to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wg300hpTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wg600hpTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr8170nTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr8175nTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr8370nTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr8600nTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr8700nTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr8750nTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr9300nTime to revision 5 days
2023-07-03Product addedCVE-2023-3332NECnot named as affected at publication, now names aterm wr9500nTime to revision 5 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →