Rt Ax3000 FirmwareOperating system · Asus

CVE-2023-31195

MEDIUM · 5.3 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to 3.0.0.4.388.23403 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
ASUS Router RT-AX3000 Firmware versions prior to 3.0.0.4.388.23403 uses sensitive cookies without 'Secure' attribute. When an attacker is in a position to be able to mount a man-in-the-middle attack, and a user is tricked to log into the affected device through an unencrypted ('http') connection, the user's session may be hijacked.

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 · high confidence

The ASUS RT-AX3000 router firmware prior to version 3.0.0.4.388.23403 sets sensitive session cookies without the 'Secure' attribute, allowing them to be transmitted over unencrypted HTTP connections. An attacker positioned for a man-in-the-middle attack can intercept these cookies and hijack user sessions.

MitigationUpgrade the router firmware to version 3.0.0.4.388.23403 or later. Avoid logging into the router over unencrypted HTTP connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rt Ax3000 FirmwareOperating system
Affected:< 3.0.0.4.388.23403

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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm router model
    Log into the router web interface or check the device label to verify the model is ASUS RT-AX3000
    Affected if The device is not an ASUS RT-AX3000 (different models have different firmware and may not be affected by this specific CVE)
  2. Check installed firmware version
    Access the router admin panel, navigate to the Firmware Version or System Information page. Compare the displayed version number to 3.0.0.4.388.23403
    Affected if The firmware version is lower than 3.0.0.4.388.23403 (for example, 3.0.0.4.388.xxxxx where xxxxx is less than 23403)
  3. Verify HTTP management is enabled
    In the router admin panel, check Network Administration or System Settings to see if HTTP (instead of HTTPS) access is allowed for the web interface
    Affected if HTTP access is enabled - the vulnerability only manifests when cookies can be transmitted over unencrypted HTTP connections

You are affected if you have an ASUS RT-AX3000 router running firmware version 3.0.0.4.388.23403 or lower AND HTTP (unencrypted) management access is enabled, allowing cookies to be sent over insecure connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.0.0.4.388.23403 or later
Fixed in 3.0.0.4.388.23403
Interim mitigation

Upgrade the router firmware to version 3.0.0.4.388.23403 or later. Avoid logging into the router over unencrypted HTTP connections.

Recommended fix High confidence

ASUS RT-AX3000 Firmware 3.0.0.4.388.23403 or later

  1. Download firmware version 3.0.0.4.388.23403 or later from the official ASUS support website for RT-AX3000
  2. Access the router's web administration interface via a wired connection
  3. Navigate to Administration > Firmware Upgrade (or similar section)
  4. Upload the downloaded firmware file and initiate the upgrade
  5. Wait for the router to reboot and verify the new firmware version is installed
  6. After upgrade, ensure you access the router via HTTPS (not HTTP) to maintain session security
Caveat Backup your router configuration before upgrading; firmware upgrades may reset some settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rt Ax3000 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31195 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31195 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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