IAM Users Without MFA
IAM users who can sign in to the AWS Management Console have no multi-factor authentication device, so a stolen or guessed password alone gives access.
| Severity | Medium |
| CVSS 3.1 | 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-308: Use of Single-factor Authentication |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1078.004 Cloud Accounts, T1110 Brute Force |
| Category | Security Misconfiguration |
Description
One or more IAM users have a console password but no multi-factor authentication (MFA) device. IAM supports passkeys and FIDO security keys, virtual authenticator applications and hardware TOTP tokens; without one, the console accepts the user's password alone.
An attacker who obtains an affected user's password, through phishing, reuse of a password exposed in another breach, or guessing, can therefore sign in to the console as that user; they also need the account ID or alias and the user name, which are often found in documentation, emails or code repositories. The attacker gains whatever the user's permissions allow, which for an administrative user means control of the account: reading and deleting data, creating users and access keys for persistence, and running resources at the organisation's expense. The finding is most significant for users with administrative or broad permissions, and in accounts where IAM users are the main way people sign in, rather than federation through IAM Identity Center or another identity provider that can enforce MFA centrally; the impact is limited where the user's permissions are narrow.
The weakness is identified from the IAM credential report, where the password_enabled column is true and mfa_active is false, or from the user list in the IAM console. Prowler, ScoutSuite and Security Hub report it as a failed check. Users who have access keys but no console password are not covered by this check, although IAM policies can still require MFA for their API calls through the aws:MultiFactorAuthPresent condition key.
Remediation
Require MFA for every IAM user who can sign in to the console:
- Register an MFA device for each affected user, preferring phishing-resistant passkeys or FIDO security keys for administrative users. IAM allows more than one MFA device per user, so a backup device can be registered.
- Attach a policy that denies all actions other than those needed to manage the user's own MFA device unless
aws:MultiFactorAuthPresentis true, so that a user who has not set up MFA can do nothing else in the console. - Remove console passwords from users who do not need console access, and delete IAM users that are no longer used.
- For the longer term, move people to federated access through
IAM Identity Centeror an external identity provider that enforces MFA, so that individual IAM users with passwords are no longer needed.
Confirm the fix by generating a new credential report (aws iam generate-credential-report, then aws iam get-credential-report) and checking that no user has password_enabled set to true with mfa_active set to false.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.