fresco

fresco copied to clipboard

Description

The latest version of Fresco uses libjpeg-turbo and specifies version 1.5.3 here. This version of libjpeg-turbo is vulnerable to CVE-2018-14498.

Reproduction

I have no example of how the vulnerability may be exploited in the context of this project.

Solution

Upgrade libjpeg-turbo to a higher version which is not associated with any CVE. The minimum version which resolves CVE-2018-14498 is 2.0.0. You may wish to go higher, but be aware that some higher versions may have their own CVE. For example, you should not upgrade to version 2.0.1 as this version has CVE-2018-20330.

Additional Information

• Fresco version: 3.0.0
• Because libjpeg-turbo is a C library and Java build tools cannot report vulnerable C libraries, do not expect a dependency scan to reveal vulnerabilities associated with the library.

@oprisnik can you take a look at this one?

Does anyone have any rough timescales on this one? We've failed a pen test due to this vulnerability and are on a really tight timescale to get it retested and passed before we can start a new contract

Thanks!

Bump

Same here

Yep, trying to close some CVE's on our app. Ideally bump libjpeg-turbo to ^3.0.0

Also trying to close some CVEs. Any updates on this?

We have this on a pen test report too.

We have this on a pen test report too. Any updates on this?

Here also with the issue reported on a pen test

any updates on this?

Any updates on this? It's been years since this vulnerability was reported.

Google app services still reports this as a vulnerability when trying to upload an application created with react-native due to the usage of this library. Is there any update?

What's the risk of having this unpatched?

@drstevenbrule the risk is a heap-based buffer over-read and application crash when libjpeg-turbo compresses certain specially-crafted 8-bit BMP files during conversion to JPEG. See NVD detail and this libjpeg-turbo commit. A good victim would be a social media application that shares user uploaded bitmap images which it converts to JPEG at display time. An attacker seeking denial of service could upload a malicious bitmap image and any user who would view that image will experience an application crash from the resulting out-of-bounds memory read during conversion.

@cortinico if Fresco never under any circumstance uses libjpeg-turbo to manipulate BMP files, then this CVE cannot be exploited. Browsing the source code I don't think it ever does, but maybe a core contributor can confirm? An example of using it to instigate the crash is here with some appropriate BMP files available here.

@cortinico @oprisnik would you take a look at https://github.com/facebook/fresco/pull/2768.

@mnt @cortinico @oprisnik Any update here? This vulnerability has been sitting for some time. Thanks!

We are planning to fix this by merging #2768.

@steelrooter when can we take a release cut to upgrade Fresco on react-native?

Closing as this was fixed in Fresco 3.2.0