Skip to content

Use of a Key Past its Expiration Date and Insufficient Session Expiration in Maddy Mail Server

Moderate severity GitHub Reviewed Published Mar 6, 2022 in foxcpp/maddy • Updated Feb 3, 2023

Package

gomod github.com/foxcpp/maddy (Go)

Affected versions

< 0.5.4

Patched versions

0.5.4

Description

Impact

Any configuration on any maddy version <0.5.4 using auth.pam is affected.

No password expiry or account expiry checking is done when authenticating using PAM.

Patches

Patch is available as part of the 0.5.4 release.

Workarounds

If /etc/shadow authentication is used, it is possible to replace auth.pam with auth.shadow which is not affected.

It is possible to blacklist expired accounts via existing filtering mechanisms (e.g. auth_map to invalid accounts in storage.imapsql).

References

For more information

If you have any questions or comments about this advisory:

References

@foxcpp foxcpp published to foxcpp/maddy Mar 6, 2022
Published to the GitHub Advisory Database Mar 7, 2022
Reviewed Mar 7, 2022
Published by the National Vulnerability Database Mar 9, 2022
Last updated Feb 3, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS score

0.104%
(44th percentile)

Weaknesses

CVE ID

CVE-2022-24732

GHSA ID

GHSA-6cp7-g972-w9m9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.