diff options
| author | Peter Marko <peter.marko@siemens.com> | 2024-12-20 16:36:27 +0100 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2024-12-20 19:47:56 -0800 |
| commit | 576b84263bac4dda26d84d116a9e7628a126f866 (patch) | |
| tree | a7acec5499e137440c718a3986cfcc25c8f29a21 | |
| parent | 607a44649189a29e6f547ce89b41ba332a45946a (diff) | |
| download | meta-openembedded-576b84263bac4dda26d84d116a9e7628a126f866.tar.gz | |
sassc: ignore CVE-2022-43357
This CVE is fixed in current libsass recipe version.
So wrapper around it will also not show this problem.
It's usual usecase is to be statically linked with libsass which is
probably the reason why this is listed as vulnerable component.
[1] links [2] as issue tracker which points to [3] as fix.
[4] as base repository for the recipe is not involved and files from [3]
are not present in this repository.
[1] https://nvd.nist.gov/vuln/detail/CVE-2022-43357
[2] https://github.com/sass/libsass/issues/3177
[3] https://github.com/sass/libsass/pull/3184
[4] https://github.com/sass/sassc/
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
| -rw-r--r-- | meta-oe/recipes-support/sass/sassc_git.bb | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/meta-oe/recipes-support/sass/sassc_git.bb b/meta-oe/recipes-support/sass/sassc_git.bb index 9bb8c76e87..94d69642a7 100644 --- a/meta-oe/recipes-support/sass/sassc_git.bb +++ b/meta-oe/recipes-support/sass/sassc_git.bb | |||
| @@ -11,4 +11,6 @@ SRCREV = "66f0ef37e7f0ad3a65d2f481eff09d09408f42d0" | |||
| 11 | S = "${WORKDIR}/git" | 11 | S = "${WORKDIR}/git" |
| 12 | PV = "3.6.2" | 12 | PV = "3.6.2" |
| 13 | 13 | ||
| 14 | CVE_STATUS[CVE-2022-43357] = "cpe-incorrect: this is CVE for libsass, not sassc wrapper" | ||
| 15 | |||
| 14 | BBCLASSEXTEND = "native" | 16 | BBCLASSEXTEND = "native" |