dbcve.org
Mt6000 FirmwareOperating system · Gl Inet

CVE-2024-28077

HIGH · 7.5 CVSS v3.1 Published 2024-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A denial-of-service issue was discovered on certain GL-iNet devices. Some websites can detect devices exposed to the external network through DDNS, and consequently obtain the IP addresses and ports of devices that are exposed. By using special usernames and special characters (such as half parentheses or square brackets), one can call the login interface and cause the session-management program to crash, resulting in customers being unable to log into their devices. This affects MT6000 4.5.6, XE3000 4.4.5, X3000 4.4.6, MT3000 4.5.0, MT2500 4.5.0, AXT1800 4.5.0, AX1800 4.5.0, A1300 4.5.0, S200 4.1.4-0300, X750 4.3.7, SFT1200 4.3.7, MT1300 4.3.10, AR750 4.3.10, AR750S 4.3.10, AR300M 4.3.10, AR300M16 4.3.10, B1300 4.3.10, MT300N-V2 4.3.10, and XE300 4.3.16.

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 vulnerability exists in the session-management program of GL-iNet devices' login interface. By submitting specially crafted usernames containing half parentheses or square brackets, an attacker can crash the session-management daemon, causing a denial of service where legitimate users cannot log into their devices. Devices exposed to the internet via DDNS are particularly vulnerable as attackers can discover them through certain websites.

MitigationRestrict external access to the admin login interface (do not expose DDNS to the internet), and apply vendor firmware updates when released. Consider network segmentation to limit exposure.

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
Mt6000 FirmwareOperating system
Affected:= 4.5.6
X3000 FirmwareOperating system
Affected:= 4.4.6
Xe3000 FirmwareOperating system
Affected:= 4.4.4
A1300 FirmwareOperating system
Affected:= 4.5.0
Ax1800 FirmwareOperating system
Affected:= 4.5.0
Axt1800 FirmwareOperating system
Affected:= 4.5.0
Mt2500 FirmwareOperating system
Affected:= 4.5.0
Mt3000 FirmwareOperating system
Affected:= 4.5.0

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

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

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. Identify GL-iNet device model
    Access the router admin interface and navigate to System Overview or Status page to view the device model name. Alternatively, check the device label or packaging.
    Affected if The device model is one of: Mt6000, X3000, Xe3000, A1300, Ax1800, Axt1800, Mt2500, or Mt3000
  2. Check installed firmware version
    In the router admin interface, go to System Overview or Firmware Upgrade section to view the current firmware version. Compare this against the affected versions: Mt6000 at 4.5.6, X3000 at 4.4.6, Xe3000 at 4.4.4, and A1300, Ax1800, Axt1800, Mt2500, Mt3000 all at 4.5.0.
    Affected if The firmware version matches exactly one of the listed affected versions
  3. Verify session-management daemon status
    Access the router via SSH or console and run: ps | grep -i session or systemctl status session-manager (command may vary by firmware). Check if the session-management process is running or has exited unexpectedly.
    Affected if The session-management daemon is not running or has crashed recently
  4. Check for internet exposure of admin interface
    Review router firewall settings and port forwarding rules. Check if DDNS is configured and accessible from the internet. Look for any port forwards or NAT rules exposing ports 80/443 to WAN.
    Affected if The admin login interface is directly accessible from the internet via DDNS or forwarded ports
  5. Examine system logs for crash events
    Access router logs via the admin interface (System Logs) or via CLI: logread or cat /var/log/messages. Search for entries related to session-manager crashes, authentication failures, or daemon restarts triggered by malformed input.
    Affected if Logs contain crash, exit, or restart events for the session-management daemon, especially if triggered by login attempts

A user is affected if they have a listed GL-iNet device model running exactly the firmware version specified, and the session-management daemon is crashed or the admin interface is exposed to the internet.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict external access to the admin login interface (do not expose DDNS to the internet), and apply vendor firmware updates when released. Consider network segmentation to limit exposure.

Fix this in Mt6000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-28077 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