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.

137 changes behind one line · newest first

SinceClear all
ChangedSourceRows

One change, in full: Package added to advisory: 129 packages named as affected in nuget. The same change in 6 advisories, across 129 packages: 137 rows in all, one per advisory and package. Drawn here as 6 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.
2022-11-01published 2022-08-30GHSA-3rq8-h3gj-r5c6CVE-2022-29117highnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.osx-arm64Days to revision 63
2022-11-01published 2022-05-24GHSA-242j-2gm6-5rwxCVE-2021-1723highnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-musl-armDays to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7moderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.linux-x64.cross.android-arm and 115 moreDays to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.linux-x64.cross.android-armDays to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.linux-x64.cross.android-arm64Days to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.linux-x64.cross.android-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.linux-x64.cross.android-x86Days to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.linux-x64.cross.browser-wasmDays to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.osx-x64.cross.android-armDays to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.osx-x64.cross.android-arm64Days to revision 161
2022-11-01published 2022-05-24GHSA-5v8v-66v8-mwm7CVE-2020-8927same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.netcore.app.runtime.aot.osx-x64.cross.android-x64Days to revision 161
108 more rows in this change are not listed here. Open all 116 rows
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmmoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-arm and 7 moreDays to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-armDays to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-arm64Days to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-musl-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.osx-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.win-armDays to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.win-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-23cv-jh4v-vffmCVE-2020-0602same package registry as the line abovemoderatenot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.win-x86Days to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmhighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-arm and 8 moreDays to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-armDays to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-arm64Days to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-musl-arm64Days to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-musl-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.osx-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.win-armDays to revision 161
2022-11-01published 2022-05-24GHSA-655q-9gvg-q4cmCVE-2020-0603same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.win-x64Days to revision 161
1 more row in this change is not listed here. Open all 9 rows
2022-11-01published 2022-05-24GHSA-r4mw-gxf7-vxr9highnot named as affected when the advisory was published, now names microsoft.windowsdesktop.app.runtime.win-x64 and 1 moreDays to revision 161
2022-11-01published 2022-05-24GHSA-r4mw-gxf7-vxr9CVE-2020-0606same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.windowsdesktop.app.runtime.win-x64Days to revision 161
2022-11-01published 2022-05-24GHSA-r4mw-gxf7-vxr9CVE-2020-0606same package registry as the line abovehighnot named as affected when the advisory was published, now names microsoft.windowsdesktop.app.runtime.win-x86Days to revision 161

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 →