Skip to content

Package added to advisory

What a record said when it was published, what it says now, and the commit that changed it.

19 changes behind one line · newest first

SinceClear all
ChangedSourceRows

One change, in full: Package added to advisory: 12 packages named as affected in packagist. The same change in 14 advisories, across 12 packages: 19 rows in all, one per advisory and package. Drawn here as 9 lines, one per package. Back to the ledger

Counted changes of "Package added to advisory", newest first, one line per change to 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.Advisory, Which advisory was edited, by its GHSA id.Package, The package the advisory names, and the registry it comes from.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-02-06published 2022-05-14GHSA-x3cf-w64x-4cp2CVE-2018-19789moderatenot named as affected when the advisory was published, now names symfony/formDays to revision 634
2024-02-06published 2022-05-17GHSA-83c3-qx27-2rwrmoderatenot named as affected when the advisory was published, now names symfony/http-foundation and 2 moreDays to revision 630
2024-02-06published 2022-05-17GHSA-83c3-qx27-2rwrCVE-2012-6431same package registry as the line abovemoderatenot named as affected when the advisory was published, now names symfony/http-foundationDays to revision 630
2024-02-06published 2022-05-17GHSA-83c3-qx27-2rwrCVE-2012-6431same package registry as the line abovemoderatenot named as affected when the advisory was published, now names symfony/routingDays to revision 630
2024-02-06published 2022-05-17GHSA-83c3-qx27-2rwrCVE-2012-6431same package registry as the line abovemoderatenot named as affected when the advisory was published, now names symfony/securityDays to revision 630
2024-02-06published 2020-03-30GHSA-m884-279h-32v2moderatenot named as affected when the advisory was published, now names symfony/error-handler and 1 morenot dated
2024-02-06published 2020-03-30GHSA-m884-279h-32v2CVE-2020-5274same package registry as the line abovemoderatenot named as affected when the advisory was published, now names symfony/error-handlernot dated
2024-02-06published 2020-03-30GHSA-m884-279h-32v2CVE-2020-5274same package registry as the line abovemoderatenot named as affected when the advisory was published, now names symfony/symfonynot dated
2024-02-06published 2022-05-17GHSA-5qp6-78pr-gv8cCVE-2013-4701highnot named as affected when the advisory was published, now names typo3/cmsDays to revision 630
2024-02-06published 2022-05-17GHSA-vc74-c4m6-9979CVE-2013-7082moderatenot named as affected when the advisory was published, now names neos/flowDays to revision 631
2024-02-06published 2021-09-30 to 2022-05-172 bandsnot named as affected when the advisory was published, now names drupal/coreDays to revision 630
2024-02-06published 2022-01-06GHSA-8cw5-rv98-5c46CVE-2019-6339same package registry as the line abovecriticalsame change as the line abovenot dated
2024-02-06published 2022-05-17GHSA-836p-6p4j-35cgCVE-2016-3164same package registry as the line abovehighsame change as the line aboveDays to revision 630
2024-02-06published 2021-09-30GHSA-xv7v-rf6g-xwrcCVE-2019-11831same package registry as the line abovecriticalsame change as the line abovenot dated
2024-02-06published 2019-10-10 to 2022-05-243 bandsnot named as affected when the advisory was published, now names drupal/drupalDays to revision 623
2024-02-06published 2022-05-24GHSA-m648-hpf8-qcjwCVE-2020-13663same package registry as the line abovehighsame change as the line aboveDays to revision 623
2024-02-06published 2021-10-12GHSA-68jc-v27h-vhmwCVE-2020-13671same package registry as the line abovehighsame change as the line abovenot dated
2024-02-06published 2022-02-12GHSA-m6q5-wv4x-fv6hCVE-2020-13668same package registry as the line abovemoderatesame change as the line abovenot dated
2024-02-06published 2019-10-10GHSA-v3f6-f29f-rgvpCVE-2017-6923same package registry as the line abovemoderatesame change as the line abovenot dated
2024-02-06published 2021-09-30GHSA-xv7v-rf6g-xwrcCVE-2019-11831same package registry as the line abovecriticalsame change as the line abovenot dated
2024-02-06published 2021-08-23 to 2022-02-10moderatenot named as affected when the advisory was published, now names contao/contaonot dated
2024-02-06published 2022-02-10GHSA-pj4j-287j-f742CVE-2018-10125same package registry as the line abovemoderatesame change as the line abovenot dated
2024-02-06published 2021-08-23GHSA-r6mv-ppjc-4hgrCVE-2021-37626same package registry as the line abovemoderatesame change as the line abovenot dated
2024-02-06published 2022-02-10GHSA-pj4j-287j-f742CVE-2018-10125moderatenot named as affected when the advisory was published, now names contao/corenot dated

Counted in advisories, never added to the CVE and KEV figures. This kind is counted once per advisory and per package, so one advisory that named four further packages counts four times. 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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →