8.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
6.5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
SINGLE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:S/C:P/I:P/A:P
0.001 Low
EPSS
Percentile
37.3%
When configuring saltstack to authentificate via the salt.auth.pam
module. The authorization of a account validity is missing. Therefore expired accounts, or accounts with expired passwords, can still login.
Configure salt with salt.auth.pam and run it with an expired account. To expire an PAM account use: chage -E0 <username>
After successfull authentication with pam_authenticate
it’s necessary to check the validity of an account with pam_acct_mgmt()
. This is done, but the return value is discarded and only the return value of pam_authenticate
is being used which results in skipping for authorization completely. Depending on how salt is configured this can become pretty severe. You don’t revoke privileges for an account without a reason. As always I assume that the salt developers could estimate the severity way better than I could, so feel free to correct it.
8.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
6.5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
SINGLE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:S/C:P/I:P/A:P
0.001 Low
EPSS
Percentile
37.3%