dbcve.org
CWE-259Weakness · CWE-259

CVE-2024-11630

HIGH · 7.3 CVSS v3.1 Published 2024-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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 vulnerability has been found in E-Lins H685, H685f, H700, H720, H750, H820, H820Q, H820Q0 and H900 up to 3.2 and classified as critical. This vulnerability affects unknown code of the component OEM Backend. The manipulation leads to hard-coded credentials. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. It is recommended to change the configuration settings. The vendor was contacted early about this disclosure but did not respond in any way.

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

Hard-coded credentials vulnerability in the OEM Backend component of E-Lins H685, H685f, H700, H720, H750, H820, H820Q, H820Q0, and H900 routers (firmware up to v3.2) allows remote attackers to bypass authentication using the embedded credentials.

MitigationImmediately change default configuration settings on all affected devices. Since the vendor did not respond, consider network segmentation, disabling remote management interfaces if not required, or replacing affected devices if patches are unavailable.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

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

  1. Identify the E-Lins router model
    Log into the router admin interface or check the device label to confirm the exact model number (H685, H685f, H700, H720, H750, H820, H820Q, H820Q0, or H900).
    Affected if The device is any of the listed models.
  2. Check the installed firmware version
    Access the router web interface (typically at 192.168.1.1 or similar) and navigate to the Status or System Information page to view the firmware version. Alternatively, check via CLI if telnet/ssh access is available.
    Affected if The firmware version is v3.2 or any version lower than v3.2.
  3. Determine if the OEM Backend component is enabled
    Check the router administration panel for settings related to 'OEM Backend', 'Remote Management', 'TR-069', 'CWMP', or 'Auto Configuration Server'. This is often found under Advanced Settings, WAN settings, or Management settings.
    Affected if The OEM Backend feature is enabled and accessible from the WAN interface.
  4. Verify remote management access exposure
    Check router firewall or port forwarding rules to see if management ports (HTTP/HTTPS on 80/443, or custom ports) are exposed to the WAN/internet. Review the WAN-facing interface configuration.
    Affected if Remote management interfaces are reachable from the internet without VPN or network segmentation.
  5. Inspect configuration for hard-coded credentials
    If you have access to the router's configuration backup file (often a .bin or .cfg file), examine it for embedded usernames and passwords that are not user-configured. Also check any backup or backup-related files stored on the device.
    Affected if The configuration file contains credentials that are identical across multiple devices or are not user-defined.

A user is affected if they have any of the listed E-Lins router models running firmware v3.2 or lower with the OEM Backend component enabled and potentially exposed to network access.

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

Immediately change default configuration settings on all affected devices. Since the vendor did not respond, consider network segmentation, disabling remote management interfaces if not required, or replacing affected devices if patches are unavailable.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11630 — 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-11630 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