Product added
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
| 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. | Record, 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 changed | Days 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-11 | CVE-2023-38380 | not named as affected at publication, now names simatic cp 1542sp-1 and 5 more | Time to revision 182 days | |
| 2024-06-11 | CVE-2023-38380 | same vendor as the line above | not named as affected at publication, now names simatic cp 1542sp-1 | Time to revision 182 days |
| 2024-06-11 | CVE-2023-38380 | same vendor as the line above | not named as affected at publication, now names simatic cp 1542sp-1 irc | Time to revision 182 days |
| 2024-06-11 | CVE-2023-38380 | same vendor as the line above | not named as affected at publication, now names simatic cp 1543sp-1 | Time to revision 182 days |
| 2024-06-11 | CVE-2023-38380 | same vendor as the line above | not named as affected at publication, now names siplus et 200sp cp 1542sp-1 irc tx rail | Time to revision 182 days |
| 2024-06-11 | CVE-2023-38380 | same vendor as the line above | not named as affected at publication, now names siplus et 200sp cp 1543sp-1 isec | Time to revision 182 days |
| 2024-06-11 | CVE-2023-38380 | same vendor as the line above | not named as affected at publication, now names siplus et 200sp cp 1543sp-1 isec tx rail | Time to revision 182 days |
| 2024-06-11 | not named as affected at publication, now names teamcenter visualization v2312 | Time to revision 63 to 308 days | ||
| 2024-06-11 | CVE-2023-38527 | same vendor as the line above | same change as the line above | Time to revision 308 days |
| 2024-06-11 | CVE-2023-38529 | same vendor as the line above | same change as the line above | Time to revision 308 days |
| 2024-06-11 | CVE-2023-38531 | same vendor as the line above | same change as the line above | Time to revision 308 days |
| 2024-06-11 | CVE-2024-26275 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26276 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26277 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | not named as affected at publication, now names jt2go | Time to revision 63 days | ||
| 2024-06-11 | CVE-2024-26275 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26276 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26277 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | not named as affected at publication, now names teamcenter visualization v14.2 | Time to revision 63 days | ||
| 2024-06-11 | CVE-2024-26275 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26276 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26277 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | not named as affected at publication, now names teamcenter visualization v14.3 | Time to revision 63 days | ||
| 2024-06-11 | CVE-2024-26275 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26276 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-26277 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2024-06-11 | CVE-2024-31484 | not named as affected at publication, now names cpcx26 central processing/communication and 3 more | Time to revision 28 days | |
| 2024-06-11 | CVE-2024-31484 | same vendor as the line above | not named as affected at publication, now names cpcx26 central processing/communication | Time to revision 28 days |
| 2024-06-11 | CVE-2024-31484 | same vendor as the line above | not named as affected at publication, now names eta4 ethernet interface iec60870-5-104 | Time to revision 28 days |
| 2024-06-11 | CVE-2024-31484 | same vendor as the line above | not named as affected at publication, now names eta5 ethernet int. 1x100tx iec61850 ed.2 | Time to revision 28 days |
| 2024-06-11 | CVE-2024-31484 | same vendor as the line above | not named as affected at publication, now names pccx26 ax 1703 pe, contr, communication element | Time to revision 28 days |
| 2024-06-11 | CVE-2023-44317 | not named as affected at publication, now names scalance wam763-1 and 9 more | Time to revision 210 days | |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44317 | same vendor as the line above | not named as affected at publication, now names scalance wum763-1 | Time to revision 210 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
| 2024-06-11 | CVE-2023-44319 | not named as affected at publication, now names scalance wam763-1 and 9 more | Time to revision 210 days | |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44319 | same vendor as the line above | not named as affected at publication, now names scalance wum763-1 | Time to revision 210 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
| 2024-06-11 | CVE-2023-44373 | not named as affected at publication, now names scalance wam763-1 and 9 more | Time to revision 210 days | |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44373 | same vendor as the line above | not named as affected at publication, now names scalance wum763-1 | Time to revision 210 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
| 2024-06-11 | CVE-2023-44374 | not named as affected at publication, now names scalance wam763-1 and 9 more | Time to revision 210 days | |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wam763-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (me) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wam766-1 eec (us) | Time to revision 210 days |
| 2024-06-11 | CVE-2023-44374 | same vendor as the line above | not named as affected at publication, now names scalance wum763-1 | Time to revision 210 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. 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 →