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

Vulnerabilities Found #414

Closed
ganeshv2911 opened this issue Apr 4, 2023 · 9 comments
Closed

Vulnerabilities Found #414

ganeshv2911 opened this issue Apr 4, 2023 · 9 comments
Assignees
Labels
security The issue is related to a security vulnerability

Comments

@ganeshv2911
Copy link

Hi Team,

In our recent scans we found the below components flagged as Vulnerabilities:
Components

openssl.cnf/openssl.cnf.dist/engines-3 OpenSSL3.0.7
ajv6.10.0
avahi-libs/0.8-r9/x86_64
ffmpeg-libs/5.1.2-r1/x86_64
libgd/2.3.3-r6/x86_64
mbedtls/2.28.2-r0/x86_64
libcrypto3/3.0.8-r0/x86_64
libssl3/3.0.8-r0/x86_64
xdg-utils/1.1.3-r4/noarch

We need to know how these components are being used in image renderer code?

Appreciate the Help.

Regards,
GV

@rhorvath rhorvath added the security The issue is related to a security vulnerability label Apr 6, 2023
@joanlopez
Copy link
Collaborator

Hi @ganeshv2911,

First of all, thanks for reporting them.

We're going to analyze our internal security scans and:

  • Bring back more information about those (if any) that directly impact the Image Renderer (exploitable through it)
  • Update the dependencies (base Docker image) and see how many of them get solved in the new release.

@AgnesToulet
Copy link
Contributor

Hi!

A new version of the image renderer has been released and contains updated libraries.

CVE-2020-27748 (xdg-utils) is still there but is related to emails (Thunderbird) and this is not used by the image renderer.

@ganeshv2911
Copy link
Author

Hi,
Can you mention what are the libraries updated ?

@AgnesToulet
Copy link
Contributor

Hi,

You can see in the changelog that, in the image renderer itself, pkg and jimp were updated.

Also, when we make a new release, the base Docker image and Chromium are updated. I don't have the list of the libraries that were updated doing that but, from the list of vulnerabilities that were present before 3.7.0 and that are now gone, I can say at least these libraries were updated: ffmpeg-libs (Chromium), http-cache-semantics (base Docker image), gnutls (base Docker image).

@ganeshv2911
Copy link
Author

Hi,
Sorry for asking again.
But in the docker file the image still the same right. (node:16-alpine AS base )
Where can I see the changed base docker image version.

@AgnesToulet
Copy link
Contributor

Yes but the base image can be updated. It's built with this Dockerfile and if you look into the file history, you can see that the NodeJS library has been updated to 16.20.0 (and the changelog for this version is here: https://github.com/nodejs/node/releases/tag/v16.20.0)

@ganeshv2911
Copy link
Author

Hi ,
Is chromium part of the base image update or it is updated separately?

@AgnesToulet
Copy link
Contributor

It's updated separately, latest version of Chromium is downloaded each time we create a new Docker image, see: https://github.com/grafana/grafana-image-renderer/blob/master/Dockerfile#L13.

@ganeshv2911
Copy link
Author

Thanks for your quick replies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security The issue is related to a security vulnerability
Projects
None yet
Development

No branches or pull requests

4 participants