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.

65 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

One change, in full: Product added: 24 products named as affected from siemens. The same change in 12 CVE records, across 24 products: 65 rows in all. Drawn here as 10 lines, one per product. Back to the ledger

Counted changes published by siemens, 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.
2024-06-11Product addedCVE-2023-38380not named as affected at publication, now names simatic cp 1542sp-1 and 5 moreTime to revision 182 days
2024-06-11same kind of change as the line aboveCVE-2023-38380same vendor as the line abovenot named as affected at publication, now names simatic cp 1542sp-1Time to revision 182 days
2024-06-11same kind of change as the line aboveCVE-2023-38380same vendor as the line abovenot named as affected at publication, now names simatic cp 1542sp-1 ircTime to revision 182 days
2024-06-11same kind of change as the line aboveCVE-2023-38380same vendor as the line abovenot named as affected at publication, now names simatic cp 1543sp-1Time to revision 182 days
2024-06-11same kind of change as the line aboveCVE-2023-38380same vendor as the line abovenot named as affected at publication, now names siplus et 200sp cp 1542sp-1 irc tx railTime to revision 182 days
2024-06-11same kind of change as the line aboveCVE-2023-38380same vendor as the line abovenot named as affected at publication, now names siplus et 200sp cp 1543sp-1 isecTime to revision 182 days
2024-06-11same kind of change as the line aboveCVE-2023-38380same vendor as the line abovenot named as affected at publication, now names siplus et 200sp cp 1543sp-1 isec tx railTime to revision 182 days
2024-06-11Product addednot named as affected at publication, now names teamcenter visualization v2312Time to revision 63 to 308 days
2024-06-11same kind of change as the line aboveCVE-2023-38527same vendor as the line abovesame change as the line aboveTime to revision 308 days
2024-06-11same kind of change as the line aboveCVE-2023-38529same vendor as the line abovesame change as the line aboveTime to revision 308 days
2024-06-11same kind of change as the line aboveCVE-2023-38531same vendor as the line abovesame change as the line aboveTime to revision 308 days
2024-06-11same kind of change as the line aboveCVE-2024-26275same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26276same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26277same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11Product addednot named as affected at publication, now names jt2goTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26275same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26276same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26277same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11Product addednot named as affected at publication, now names teamcenter visualization v14.2Time to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26275same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26276same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26277same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11Product addednot named as affected at publication, now names teamcenter visualization v14.3Time to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26275same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26276same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11same kind of change as the line aboveCVE-2024-26277same vendor as the line abovesame change as the line aboveTime to revision 63 days
2024-06-11Product addedCVE-2024-31484not named as affected at publication, now names cpcx26 central processing/communication and 3 moreTime to revision 28 days
2024-06-11same kind of change as the line aboveCVE-2024-31484same vendor as the line abovenot named as affected at publication, now names cpcx26 central processing/communicationTime to revision 28 days
2024-06-11same kind of change as the line aboveCVE-2024-31484same vendor as the line abovenot named as affected at publication, now names eta4 ethernet interface iec60870-5-104Time to revision 28 days
2024-06-11same kind of change as the line aboveCVE-2024-31484same vendor as the line abovenot named as affected at publication, now names eta5 ethernet int. 1x100tx iec61850 ed.2Time to revision 28 days
2024-06-11same kind of change as the line aboveCVE-2024-31484same vendor as the line abovenot named as affected at publication, now names pccx26 ax 1703 pe, contr, communication elementTime to revision 28 days
2024-06-11Product addedCVE-2023-44317not named as affected at publication, now names scalance wam763-1 and 9 moreTime to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44317same vendor as the line abovenot named as affected at publication, now names scalance wum763-1Time to revision 210 days
2 more rows in this change are not listed here. Open all 10 rows
2024-06-11Product addedCVE-2023-44319not named as affected at publication, now names scalance wam763-1 and 9 moreTime to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44319same vendor as the line abovenot named as affected at publication, now names scalance wum763-1Time to revision 210 days
2 more rows in this change are not listed here. Open all 10 rows
2024-06-11Product addedCVE-2023-44373not named as affected at publication, now names scalance wam763-1 and 9 moreTime to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44373same vendor as the line abovenot named as affected at publication, now names scalance wum763-1Time to revision 210 days
2 more rows in this change are not listed here. Open all 10 rows
2024-06-11Product addedCVE-2023-44374not named as affected at publication, now names scalance wam763-1 and 9 moreTime to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (me)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eec (us)Time to revision 210 days
2024-06-11same kind of change as the line aboveCVE-2023-44374same vendor as the line abovenot named as affected at publication, now names scalance wum763-1Time to revision 210 days
2 more rows in this change are not listed here. Open all 10 rows

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →