libpam: mark CVE-2025-6018 as not applicable
PATCH 1/1 libpam: mark CVE-2025-6018 as not applicable
CVE-2025-6018 is a local privilege escalation in PAM that requires user_readenv=1 to be enabled in the PAM configuration. The default configuration does not enable reading user environment files (user_readenv is 0 by default). Hence this vulnerability cannot be exploited using the default configuration.
--- meta/recipes-extended/pam/libpam_1.7.1.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-extended/pam/libpam_1.7.1.bb +2 -0
@@ -26,6 +26,8 @@ SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/Linux-PAM-${PV}.tar.xz \ SRC_URI[sha256sum] = "21dbcec6e01dd578f14789eac9024a18941e6f2702a05cf91b28c232eeb26ab0" +CVE_STATUS[CVE-2025-6018] = "not-applicable-config: Default PAM config does not use user_readenv=1" + DEPENDS = "bison-native flex-native libxml2-native virtual/crypt" EXTRA_OEMESON = "-Ddocs=disabled -Dsecuredir=${base_libdir}/security"
base-commit: 416731b8756cd2689055ada2deaff48c7751d3b9
Signature · 1 line
2.34.1
NVD shows following CPE for this CVE:
cpe:2.3:a:suse:pam-config:1.1.8-24.71.1:*:*:*:*:*:*:*
So we don't need to ignore it as it won't show up in Yocto CVE reports. Next time I'd search for obsolete CVE_STATUS entries I'd erase this commit. What's the reason for this patch?
What would be worth investigating is CVE-2024-10041 which is reported for libpam recipe. Unfortunately not reported on autobuilder as it's not using systemd+pam distro config.
Peter
Quoted 40 lines
-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of Anders Heimer
Sent: Tuesday, October 21, 2025 15:59
To: [email protected]
Cc: Anders Heimer <[email protected]>
Subject: [OE-core][PATCH] libpam: mark CVE-2025-6018 as not applicableCVE-2025-6018 is a local privilege escalation in PAM that requires
user_readenv=1to be enabled in the PAM configuration. The default configuration does not enable reading user environment files (user_readenvis 0 by default). Hence this vulnerability cannot be exploited using the default configuration.Signed-off-by Anders Heimer <[email protected]>--- meta/recipes-extended/pam/libpam_1.7.1.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes- renamed from meta/recipes-extended/pam/libpam_1.7.1.bb +0
-0extended/pam/libpam_1.7.1.bb
index8d9ea27028..42b50a8c22100644meta/recipes-extended/pam/libpam_1.7.1.bb +0
-0@@ -26,6 +26,8 @@ SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/Linux- PAM-${PV}.tar.xz \ SRC_URI[sha256sum] ="
21dbcec6e01dd578f14789eac9024a18941e6f2702a05cf91b28c232eeb26ab0"+CVE_STATUS[CVE-2025-6018] = "not-applicable-config: Default PAM config does not use user_readenv=1"
+
DEPENDS = "bison-native flex-native libxml2-native virtual/crypt"
EXTRA_OEMESON= "-Ddocs=disabled -Dsecuredir=${base_libdir}/security"base-commit:
416731b8756cd2689055ada2deaff48c7751d3b9--
2.34.1
Quoted 6 lines · Peter Marko via lists.openembedded.org
NVD shows following CPE for this CVE:
cpe:2.3:a:suse:pam-config:1.1.8-24.71.1:*:*:*:*:*:*:*So we don't need to ignore it as it won't show up in Yocto CVE reports. Next time I'd search for obsolete
CVE_STATUSentries I'd erase this commit. What's the reason for this patch?
Thanks for the clarification.
I agree, CVE-2025-6018 doesn’t hit Yocto’s libpam.
My patch came from our internal scanner flagging the CVE; it doesn’t use Yocto’s product mapping and raised a false positive.
Br, Anders
Quoted 55 lines
What would be worth investigating is CVE-2024-10041 which is reported for libpam recipe. Unfortunately not reported on autobuilder as it's not using systemd+pam distro config.
Peter
Quoted 35 lines
-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of Anders Heimer
Sent: Tuesday, October 21, 2025 15:59
To: [email protected]
Cc: Anders Heimer <[email protected]>
Subject: [OE-core][PATCH] libpam: mark CVE-2025-6018 as not applicableCVE-2025-6018 is a local privilege escalation in PAM that requires
user_readenv=1to be enabled in the PAM configuration. The default configuration does not enable reading user environment files (user_readenvis 0 by default). Hence this vulnerability cannot be exploited using the default configuration.Signed-off-by Anders Heimer <[email protected]>--- meta/recipes-extended/pam/libpam_1.7.1.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes- renamed from meta/recipes-extended/pam/libpam_1.7.1.bb +0
-0extended/pam/libpam_1.7.1.bb
index8d9ea27028..42b50a8c22100644meta/recipes-extended/pam/libpam_1.7.1.bb +0
-0@@ -26,6 +26,8 @@ SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/Linux- PAM-${PV}.tar.xz \ SRC_URI[sha256sum] ="
21dbcec6e01dd578f14789eac9024a18941e6f2702a05cf91b28c232eeb26ab0"+CVE_STATUS[CVE-2025-6018] = "not-applicable-config: Default PAM config does not use user_readenv=1"
+
DEPENDS = "bison-native flex-native libxml2-native virtual/crypt"Quoted 5 lines
EXTRA_OEMESON = "-Ddocs=disabled -Dsecuredir=${base_libdir}/security"base-commit:
416731b8756cd2689055ada2deaff48c7751d3b9--
2.34.1-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#225151): https://lists.openembedded.org/g/openembedded-core/message/225151
Mute This Topic: https://lists.openembedded.org/mt/115873392/7170510
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-