Product added
One change, in full: Product added: 17 products named as affected in CVE-2023-44318. The same change in 1 CVE record, across 17 products: 17 rows in all. Back to all 27 products in this change · 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. |
|---|---|---|---|---|
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xb206-2 (sc) | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xb206-2 (st/bfoc) | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xb206-2 ld | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xb206-2 sc | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xb206-2 st | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xb206-2ld | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xf204g | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp208g | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp208g eec | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp208g poe eec | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp208g pp | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp216 (v2) | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp216eec (v2) | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp216g | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp216g eec | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp216g poe eec | Time to revision 637 days | |
| 2025-08-12 | CVE-2023-44318 | not named as affected at publication, now names scalance xp216poe eec (v2) | Time to revision 637 days |
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.
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 →