Security Fix

[kieferrm]

Details in https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2020-1416

[MLefebvreICO]

Just received update 1.47.1 linking to this issue, but it doesn't have details 😐

[kieferrm]

I updated the link. The MITRE copy is not yet updated.

[aaomidi]

The link currently just goes to this milestone (https://github.com/microsoft/vscode/milestone/128), is that expected?

[vp2177]

Details in https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2020-1416

That page is currently empty, so is https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1416

However, if anyone is wondering, just google (bing?) the CVE number.

[jlk]

The milestone page is "empty," but if you click "closed" you'll see it. Probably should tweak the link to show closed issues.

[wwahammy]

Is there a commit/PR we can see fixing this bug? It's not super helpful to know a CVE existed if we can't verify that it was fixed properly.

[ExE-Boss]

@wwahammy It seems like the bug was in the closed source vscode‑distro component: 1.47.0...1.47.1.

[wwahammy]

Ah, so there's some proprietary software that VSCode uses that apparently does something which can lead to a security hole. We don't know what it does or how risky it is to run.

[jlk]

A thumbs down isn't enough on this one. There's zero tolerance for backwater attitude @mahen23. Reporting.