Product added
One change, in full: Product added: 33 products named as affected from poly. The same change in 4 CVE records, across 33 products: 100 rows in all. Drawn here as 4 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-01-09 | CVE-2023-4462 | VulDB | not named as affected at publication, now names ccx 350 and 32 more | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4462 | same vendor as the line above | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 25 more rows in this change are not listed here. Open all 33 rows → | ||||
| 2024-01-09 | CVE-2023-4464 | VulDB | not named as affected at publication, now names ccx 350 and 32 more | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4464 | same vendor as the line above | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 25 more rows in this change are not listed here. Open all 33 rows → | ||||
| 2024-01-09 | CVE-2023-4465 | VulDB | not named as affected at publication, now names ccx 350 and 32 more | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names ccx 350 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names ccx 500 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names ccx 505 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names ccx 700 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names edge e100 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names edge e220 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names edge e300 | Time to revision 11 days |
| 2024-01-09 | CVE-2023-4465 | same vendor as the line above | not named as affected at publication, now names edge e320 | Time to revision 11 days |
| 25 more rows in this change are not listed here. Open all 33 rows → | ||||
| 2024-01-09 | CVE-2023-4468 | VulDB | not named as affected at publication, now names trio 8500 | Time to revision 11 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. 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 →