Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2023-5217 (libvpx heap buffer overflow) tracking #258048

Open
35 of 65 tasks
xyzeva opened this issue Sep 29, 2023 · 59 comments
Open
35 of 65 tasks

CVE-2023-5217 (libvpx heap buffer overflow) tracking #258048

xyzeva opened this issue Sep 29, 2023 · 59 comments
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems

Comments

@xyzeva
Copy link

xyzeva commented Sep 29, 2023

CVE-2023-5217 is a heap buffer overflow in libvpx's VP8 encoder, as many things such as electron and more are being tracked in this issue, so we can fix them in nixpkgs.

This vulnerability is yet to be rated, but we can assume (as its a heap buffer overflow), that it might be a big deal.

Current status

We currently have patched the libvpx package with #257941, vendored dependencies are tracked below.

How to help

  • Review/merge any nixpkgs PR that you see pending in the task list below.
  • If you have an idea of how to fix/address the vulnerability in any of the packages listed in the task list below, don't hesitate to post a comment here and send pull requests! Feel free to cc me on PRs so I can make sure they're tracked and they don't get lost.

Task list

This task list may or may not be complete, if you think we are missing something, please feel free to cc me! Here is the scan ran by @delroth for vulnerable dependencices

@mweinelt mweinelt pinned this issue Sep 29, 2023
@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@Kiwi: simplenote, binary provenance, package seems obsolete

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@maxhille: aether, binary provenance, package seems obsolete

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@06kellyjac: octant-desktop, binary provenance, upstream is archived

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@noneucat: polar-bookshelf, binary provenance, package seems obsolete

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@WolfangAukang: indigenous-desktop, binary provenance, package seems obsolete

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@Mic92, @equirosa, @urandom2: signal-desktop, binary provenance, update available, priority is high

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@Mic92, @equirosa, @urandom2: signal-desktop-beta, binary provenance, update available, priority is high

@equirosa
Copy link
Contributor

equirosa commented Sep 29, 2023 via email

@WolfangAukang
Copy link
Contributor

@WolfangAukang: indigenous-desktop, binary provenance, package seems obsolete

Not obsolete, they changed the repo name. I can build it from source, but the problem is that it does not work with an Electron version superior to 19.

@WolfangAukang
Copy link
Contributor

Regarding threema-desktop (I'm the maintainer), there was a similar issue (#254798) that asked to remove lib/threema/threema-web, but as this package is using the bundled electron, it wasn't necessary to keep tracking.

Still I have this PR open that removes that component #255899

@MikaelFangel
Copy link
Contributor

Brave is being updated in this PR #258060

@WolfangAukang
Copy link
Contributor

WolfangAukang commented Sep 29, 2023

Regarding thedesk (I'm the maintainer), this is a similar case as threema-desktop: application is using bundled electron version but the package contains the binary from the deb file.

PR: #258075

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

@travisbhartwell, @manveru, @prusnak: could we get electron fixes underway?

@mweinelt
Copy link
Member

mweinelt commented Sep 29, 2023

@WolfangAukang: indigenous-desktop, binary provenance, package seems obsolete

Not obsolete, they changed the repo name. I can build it from source, but the problem is that it does not work with an Electron version superior to 19.

Then it should be marked knownVulnerable, because they use an end-of-life and vulnerable electron version. Please make that happen if you are opposed to removing it.

@WolfangAukang
Copy link
Contributor

@WolfangAukang: indigenous-desktop, binary provenance, package seems obsolete

Not obsolete, they changed the repo name. I can build it from source, but the problem is that it does not work with an Electron version superior to 19.

Then it should be marked knownVulnerable, because they use an end-of-life and vulnerable electron version. Please make that happen if you are opposed to removing it.

You mean knownVulnerabilities? Not able to find any examples with knownVulnerable.

@xyzeva
Copy link
Author

xyzeva commented Sep 29, 2023

New logs starting up by @delroth, should be more usable for reading seashell link

@rhysmdnz
Copy link
Contributor

@vcunat
Copy link
Member

vcunat commented Oct 1, 2023

In addition to the VP8 CVE above, there's now a VP9 CVE #258295 so maybe updating everything will need to be redone again?

@xyzeva
Copy link
Author

xyzeva commented Oct 1, 2023

In addition to the VP8 CVE above, there's now a VP9 CVE #258295 so maybe updating everything will need to be redone again?

We are talking about what to do with the new CVE on the matrix room, we are going to use the same tracking issue, probably

@i077
Copy link
Contributor

i077 commented Oct 6, 2023

I think it is based on XUL, but I think the version of Firefox that comes from is very old. In the JS console in version 6.0.26, Services.appinfo.platformVersion evaluates to "60.9.0", but running the same in the browser console of the most recent release of Firefox evaluates to "118.0.1". Firefox 60.9.0 was released in September 2019. I don't know exactly how the scan was done, as the link to the scan results in the OP is broken.

I can contact their security email or post in the forums about this, but I'm not really sure what the best course of action here is in the meantime. There is Zotero 7 in beta, which patched this vulnerability in a recent build.

@NickCao
Copy link
Member

NickCao commented Oct 6, 2023

qtwebengine uses system libvpx thus should not be affected.

@MikaelFangel
Copy link
Contributor

I have applied a patch for the CVE in freeswitch in this pr: #259881

@MikaelFangel
Copy link
Contributor

Suggesting to remove simplenote in: #259889

@MikaelFangel
Copy link
Contributor

I looked at mattermost-desktop, and it doesn't use the shipped Electron version, rather it uses the Electron_26 from nixpkgs. Thus, if I haven't missed anything, it should be resolved, right?

See the line here. 😃

@MikaelFangel
Copy link
Contributor

MikaelFangel commented Oct 11, 2023

Also should mullvad-vpn not be on the list? It was also found by the vendoring checker https://clbin.com/haJzA. It has an upstream release bundling a new Electron version.

And the pr updating it can be found here #260407

@maxhille
Copy link
Contributor

@xyzeva aether is now removed from master by #258556

@qbit
Copy link
Contributor

qbit commented Oct 13, 2023

For tidal-hifi there is a push to get it building from source: #252307 - I am not versed enough to be able to help.. maybe someone else can?

@MikaelFangel
Copy link
Contributor

Mark figma-linux as vulnerable to this CVE in #261404 until fix is available.

Maintainer will update on next release see: Figma-Linux/figma-linux#341 (comment)

@MikaelFangel
Copy link
Contributor

MikaelFangel commented Oct 20, 2023

I suggest marking pulsar, as vulnerable in #262376 because it uses a very outdated version of electron and doesn't seem to plan to bundle a new version anytime soon.

@MikaelFangel
Copy link
Contributor

MikaelFangel commented Oct 21, 2023

Update pycharm here: #262418

And idea was updated by this pr: #260965

@MikaelFangel
Copy link
Contributor

MikaelFangel commented Oct 21, 2023

Have opened a draft pr fixing nwjs #262424, but I still need to do some more testing to ensure nothing breaks.

Edit
Corrected the pr, so it points to the pr...

@FliegendeWurst FliegendeWurst added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Oct 21, 2023
i077 added a commit to i077/nixpkgs that referenced this issue Oct 22, 2023
Zotero 6 is based on Firefox 60 and has not patched this vulnerability.
The next version is based on Firefox 102 (ESR) and has patched this, but
is is still in beta.

See also NixOS#258048.
@i077
Copy link
Contributor

i077 commented Oct 22, 2023

The current stable version of Zotero, based on Firefox 60 as discussed earlier here, is not going to get patched from what I can tell, so #262808 marks it as vulnerable until Zotero 7 hits GA.

github-actions bot pushed a commit that referenced this issue Oct 22, 2023
Zotero 6 is based on Firefox 60 and has not patched this vulnerability.
The next version is based on Firefox 102 (ESR) and has patched this, but
is is still in beta.

See also #258048.

(cherry picked from commit 9438baa)
@K900 K900 unpinned this issue Nov 1, 2023
@Inkbottle007
Copy link

The current stable version of Zotero, based on Firefox 60 as discussed earlier here, is not going to get patched from what I can tell, so #262808 marks it as vulnerable until Zotero 7 hits GA.

Hi, as much as I would love to see Zotero 7 come to GA, it seems Zotero 6 has been patched: "Changes in 6.0.30 (November 2, 2023), [Security] Disabled libvpx support (CVE-2023-5217)" (https://www.zotero.org/support/changelog).

@camillemndn
Copy link
Contributor

The current stable version of Zotero, based on Firefox 60 as discussed earlier here, is not going to get patched from what I can tell, so #262808 marks it as vulnerable until Zotero 7 hits GA.

Hi, as much as I would love to see Zotero 7 come to GA, it seems Zotero 6 has been patched: "Changes in 6.0.30 (November 2, 2023), [Security] Disabled libvpx support (CVE-2023-5217)" (https://www.zotero.org/support/changelog).

Hi, for those interested, I managed to package Zotero 7 built from source in https://github.com/camillemndn/nixos-config/tree/main/pkgs/applications/office/zotero, but I could not upstream it since it is based on Firefox 102 which is already deprecated...

@shlevy
Copy link
Member

shlevy commented Nov 7, 2023

Opened #266033 to update Zotero 6

@Inkbottle007
Copy link

Hi, for those interested, I managed to package Zotero 7 built from source in https://github.com/camillemndn/nixos-config/tree/main/pkgs/applications/office/zotero, but I could not upstream it since it is based on Firefox 102 which is already deprecated...

Good job building Zotero 7 from source. Zotero seems like a Heath Robinson machine and the only way to distribute is is through its prebuilt which is what the Zotero 6 nixos package is doing I understand. I don't know why they need to vendor Firefox but that's another story.

@samueldr samueldr added the 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems
Projects
None yet
Development

No branches or pull requests