dbcve.org
Remote Access Server FirmwareOperating system · Etictelecom

CVE-2024-26153

HIGH · 7.4 CVSS v3.1 Published 2025-01-17
Fix available
A fix is available. Upgrade to 4.9.19 or later.
See remediation →
81/100
Remediation priority · High
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
All versions of ETIC Telecom Remote Access Server (RAS) prior to 4.9.19 are vulnerable to cross-site request forgery (CSRF). An external attacker with no access to the device can force the end user into submitting a "setconf" method request, not requiring any CSRF token, which can lead into denial of service on the device.

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

ETIC Telecom Remote Access Server versions before 4.9.19 lack CSRF protection on the 'setconf' method, allowing external attackers to trick authenticated users into submitting unintended configuration requests that cause denial of service.

MitigationUpdate to ETIC Telecom RAS version 4.9.19 or later which implements CSRF token validation for the setconf method.

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
Remote Access Server FirmwareOperating system
Affected:< 4.9.19

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
Required
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Check the installed firmware version
    Access the ETIC Telecom RAS web interface (usually at https://<device-ip>/ or http://<device-ip>/) and navigate to System > About or System > Information page. Alternatively, log into the device via SSH or console and run: show version or cat /proc/version. Look for the firmware version number.
    Affected if The firmware version is displayed as anything less than 4.9.19 (for example, 4.9.18, 4.8.x, 4.7.x, etc.)
  2. Confirm the web management interface is accessible
    Attempt to reach the RAS web interface from a browser or using curl: curl -k https://<device-ip>/ or curl http://<device-ip>/. Check if the login page or status page loads.
    Affected if The web interface is accessible and accepts authentication, meaning authenticated users could be targeted by CSRF attacks
  3. Identify if the setconf method endpoint exists
    After logging into the web interface, examine HTTP requests when accessing configuration pages, or attempt a direct request to a potential setconf endpoint such as: curl -k -X POST https://<device-ip>/setconf or check the API documentation if available. Look for any configuration-related POST endpoints.
    Affected if The setconf method or similar configuration update endpoint is reachable without requiring a unique per-request CSRF token
  4. Verify CSRF protection is not implemented
    Log into the web interface and inspect the HTML source of any configuration form. Look for hidden input fields containing CSRF tokens (commonly named csrf_token, token, nonce, _token, or similar). Also check request headers for X-CSRF-Token or similar custom headers. Submit a configuration change and observe if a token is required.
    Affected if Configuration forms submit without requiring a unique CSRF token in the request (no token field found in HTML and no token header required)

A user is affected if the RAS firmware version is below 4.9.19 AND the web management interface is accessible, since the lack of CSRF protection on the setconf method can then be exploited.

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 4.9.19 or later
Fixed in 4.9.19
Interim mitigation

Update to ETIC Telecom RAS version 4.9.19 or later which implements CSRF token validation for the setconf method.

Recommended fix High confidence

4.9.19

  1. 1. Backup the current RAS configuration before initiating any upgrade.
  2. 2. Obtain the fixed firmware version 4.9.19 or later from the official ETIC Telecom vendor website or support channels.
  3. 3. Access the Remote Access Server administrative interface.
  4. 4. Navigate to the firmware upgrade or system update section of the management interface.
  5. 5. Upload the firmware file (version 4.9.19 or later) and initiate the upgrade process.
  6. 6. Allow the device to complete the firmware installation and automatic reboot.
  7. 7. After the device restarts, verify the firmware version displays as 4.9.19 or later in the system information.
  8. 8. Restore the previously backed up configuration if needed and verify normal operation.

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

Fix this in Remote Access Server Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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