Debian Fixes pam-mysql NULL-Password Authentication Handling

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Update trixie pam-mysql to 0.8.2-2.1+deb13u1, review NULL-password policy, and verify authentication behavior through each affected PAM service.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify trixie hosts using pam_mysql, PAM service stacks, MySQL-backed identities, module options and administrators responsible for access recovery. Determine whether relevant accounts have NULL passwords and how each caller uses PAM_DISALLOW_NULL_AUTHTOK. Do not extend the trixie version to other Debian releases. Install the Debian security package and review whether nullok is deliberately enabled. Preserve the required prohibition of NULL passwords in each service’s policy. Test intended acceptance and rejection using authorized test accounts, retain package and configuration evidence, and monitor authentication failures after rollout.

Open the authoritative advisory

Last verified: 2026-11-20 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopepam-mysql on Debian 13 trixie
AdvisoryDSA-6643-1
CVECVE-2026-124749
Authoritative release date2026-11-19T20:18:29Z — official Debian security-announcement message Date header.
Authority revision dateNo separate material revision is stated for this release.
Affected versionsDebian trixie pam-mysql packages before 0.8.2-2.1+deb13u1; incorrect handling of PAM_DISALLOW_NULL_AUTHTOK can authenticate users with NULL passwords.
Fixed versionpam-mysql 0.8.2-2.1+deb13u1 for Debian trixie
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

Debian corrected NULL-password handling and introduced the nullok option. Explicitly enabling nullok permits NULL-password authentication only when the PAM caller does not prohibit it.

What To Validate Now

  1. Inventory. Identify trixie hosts using pam_mysql, PAM service stacks, MySQL-backed identities, module options and administrators responsible for access recovery.
  2. Establish applicability. Determine whether relevant accounts have NULL passwords and how each caller uses PAM_DISALLOW_NULL_AUTHTOK. Do not extend the trixie version to other Debian releases.
  3. Remediate. Install the Debian security package and review whether nullok is deliberately enabled. Preserve the required prohibition of NULL passwords in each service’s policy.
  4. Validate. Test intended acceptance and rejection using authorized test accounts, retain package and configuration evidence, and monitor authentication failures after rollout.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Keep an independent administrative session or recovery path during PAM changes. Avoid weakening authentication merely to restore a previously accepted NULL-password workflow.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.