CVE-2024-28325
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAsus RT-N12+ B1 router stores credentials in cleartext, which could allow local attackers to obtain unauthorized access and modify router settings.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Asus RT-N12+ B1 router stores user credentials in cleartext format within its firmware or configuration storage. A local attacker with access to the device's storage (e.g., via physical access, SD card, or firmware extraction) can read these plaintext credentials and use them to authenticate to the router's administrative interface without triggering any security controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelCheck the device label on the router or log into the administrative web interface and look for the model number displayed on the status or administration page.Affected if The device is an Asus RT-N12+ B1 router.
-
Obtain a firmware image or configuration backupDownload the latest firmware from the Asus support site, or if you have admin access, export the router configuration from the Administration > System section of the web interface.Affected if You have access to the firmware image file or the configuration backup file (.cfg).
-
Search firmware for plaintext credentialsUse a tool like strings, binwalk, or a hex editor to extract and search the firmware image for readable password patterns. Look for the admin username and any passwords appearing in cleartext within the filesystem.Affected if The firmware contains plaintext strings matching the router admin password or user-defined credentials.
-
Examine the configuration backup fileIf you exported a configuration file, open it in a text editor and search for password-related fields. Look for tags like <password>, <pwd>, or similar and check if the values are readable text rather than hashed or encrypted strings.Affected if The configuration file contains password fields with plaintext values.
-
Verify password storage formatIf you can access the router's NVRAM or storage directly (via UART/JTAG or by extracting the flash memory), examine the file where credentials are stored. Check whether the password appears as raw text or as a hash/encrypted value.Affected if Passwords are stored as readable plaintext rather than being hashed (e.g., bcrypt, scrypt) or encrypted.
You are affected if you are using an Asus RT-N12+ B1 router and can extract plaintext credentials from its firmware image, configuration backup, or device storage.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAsus should implement proper credential hashing (e.g., bcrypt, scrypt) or encryption for stored passwords. Users should avoid storing sensitive credentials on the device and change default passwords immediately. Until a firmware patch is available, network segmentation can limit the impact of local attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data