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.

21 changes behind one line · newest firstCSVJSONRSS

Since

One change, in full: Product added: 21 products named as affected in CVE-2023-1424. Products named as affected in 1 CVE record, across 21 products: 21 rows in all, one per record and product. Back to the ledger

Counted changes, newest first, one line per change to a CVE record or a GHSA advisory, 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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.Vendor or package, 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-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r00cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r01cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r02cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r04cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r04encpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08encpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08pcpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08sfcpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120encpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120pcpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120sfcpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16encpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16pcpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16sfcpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32cpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32encpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32pcpuDays to revision 44
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32sfcpuDays to revision 44

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

Data sources and quality

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 →

Check my CVEs against these changes →