NVD / CVE Program· CNA twcert

CVE-2024-3080: ASUS Router - Improper Authentication

Noroxi assessment

Priority: Plan (action score 52/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 43.4% (FIRST EPSS); higher than 98.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Certain ASUS router models have authentication bypass vulnerability, allowing unauthenticated remote attackers to log in the device.

CriticalCVSS 9.8 · v3.1—Proof of concept No fix recorded

BDU:2024-05572

Published: Jun 13, 2024
Updated: Jun 17, 2026
EPSS: 43.4% · 98th percentile
CWE: CWE-287

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 13 / 30 · 43.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · twcert: 9.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
asus	rt-ax58u firmware	cpe:2.3:o:asus:rt-ax58u_firmware
asus	rt-ax88u firmware	cpe:2.3:o:asus:rt-ax88u_firmware
asus	rt-ax57 firmware	cpe:2.3:o:asus:rt-ax57_firmware
asus	rt-ac86u firmware	cpe:2.3:o:asus:rt-ac86u_firmware
asus	rt-ac68u firmware	cpe:2.3:o:asus:rt-ac68u_firmware
asus	zenwifi xt8 firmware	cpe:2.3:o:asus:zenwifi_xt8_firmware
asus	zenwifi xt8 v2 firmware	cpe:2.3:o:asus:zenwifi_xt8_v2_firmware

Versions reported by the vendor

Affected version ranges reported by the assigning authority (twcert). Independent of NVD's CPE analysis and usually ahead of it.

ASUS RT-AC68U
- earlier and later · up to and including 3.0.0.4.386_51668affected
ASUS RT-AC86U
- earlier and later · up to and including 3.0.0.4.386_51915affected
ASUS RT-AX57
- earlier and later · up to and including 3.0.0.4.386_52294affected
ASUS RT-AX58U
- earlier and later · up to and including 3.0.0.4.388_23925affected
ASUS RT-AX88U
- earlier and later · up to and including 3.0.0.4.388_24198affected
ASUS ZenWiFi XT8
- earlier and later · up to and including 3.0.0.4.388_24609affected
ASUS ZenWiFi XT8 V2
- earlier and later · up to and including 3.0.0.4.388_24609affected

Same product

asus: all records

Other highest-scoring records for the same primary product.

CVE-2024-3079ASUS Router - Stack-based Buffer Overflow
28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2024-3080	—

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2024-30790 days apartASUS Router - Stack-based Buffer Overflow
28Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0700 · Jun 14, 2024(ASUS Güvenlik Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

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

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

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

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.twcert.org.tw/en/cp-139-7860-760b1-2.html

Show all references (1 more)

www.twcert.org.tw/tw/cp-132-7859-0e104-1.html

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records