Skip to contentSkip to conversation

package/sane-backends: update CPE

PATCH Applied Thomas Perale via buildroot 2 participants 3 messages Jun 2 – Jun 12

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 package/sane-backends: update CPE

The CPE 'sane-backends_project:sane-backends' only has a single CVE assigned in 2017 while 'sane-project:sane_backends' has 9 since 2017 [1].

See the package CVE history at [2].

[1] https://nvd.nist.gov/vuln/detail/CVE-2023-46047
[2] https://security-tracker.debian.org/tracker/source-package/sane-backends

---
 package/sane-backends/sane-backends.mk | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
package/sane-backends/sane-backends.mk +2 -1
index fe89e7747d..de1375550c 100644
@@ -10,7 +10,8 @@ SANE_BACKENDS_SITE = \
 SANE_BACKENDS_CONFIG_SCRIPTS = sane-config
 SANE_BACKENDS_LICENSE = GPL-2.0+
 SANE_BACKENDS_LICENSE_FILES = COPYING
-SANE_BACKENDS_CPE_ID_VALID = YES
+SANE_BACKENDS_CPE_ID_VENDOR = sane-project
+SANE_BACKENDS_CPE_ID_PRODUCT = sane_backends
 SANE_BACKENDS_INSTALL_STAGING = YES
 
 SANE_BACKENDS_CONF_OPTS = \
Signature · 6 lines
2.54.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#1 lore raw
Quoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Perale via buildroot <[email protected]> writes:

The CPE 'sane-backends_project:sane-backends' only has a single CVE assigned in 2017 while 'sane-project:sane_backends' has 9 since 2017 [1].

Quoted 6 lines

See the package CVE history at [2].

[1] https://nvd.nist.gov/vuln/detail/CVE-2023-46047
[2] https://security-tracker.debian.org/tracker/source-package/sane-backends

Committed, thanks.

Signature · 5 lines
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#2 lore raw
In reply to Thomas Perale via buildroot

In reply of:

Quoted 10 lines

The CPE 'sane-backends_project:sane-backends' only has a single CVE assigned in 2017 while 'sane-project:sane_backends' has 9 since 2017 [1].

See the package CVE history at [2].

[1] https://nvd.nist.gov/vuln/detail/CVE-2023-46047
[2] https://security-tracker.debian.org/tracker/source-package/sane-backends

Applied to 2025.02.x & 2026.02.x. Thanks

Quoted 25 lines
---
 package/sane-backends/sane-backends.mk | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
package/sane-backends/sane-backends.mk +2 -1
index fe89e7747d..de1375550c 100644
@@ -10,7 +10,8 @@ SANE_BACKENDS_SITE = \
 SANE_BACKENDS_CONFIG_SCRIPTS = sane-config
 SANE_BACKENDS_LICENSE = GPL-2.0+
 SANE_BACKENDS_LICENSE_FILES = COPYING
-SANE_BACKENDS_CPE_ID_VALID = YES
+SANE_BACKENDS_CPE_ID_VENDOR = sane-project
+SANE_BACKENDS_CPE_ID_PRODUCT = sane_backends
 SANE_BACKENDS_INSTALL_STAGING = YES
 
 SANE_BACKENDS_CONF_OPTS = \
Signature · 6 lines
2.54.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot