CVE-2024-26157
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 · uneditedAll versions of ETIC Telecom Remote Access Server (RAS) prior to 4.5.0 are vulnerable to reflected cross site scripting (XSS) attacks in get view method under view parameter. The ETIC RAS web server uses dynamic pages that get their input from the client side and reflect the input in their response to the client.
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 confidenceETIC Telecom RAS versions before 4.5.0 contain a reflected XSS vulnerability in the 'get view' method where the 'view' parameter is not properly sanitized before being reflected in the HTTP response, allowing injection of malicious script content.
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< 4.5.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ETIC Telecom RAS firmware versionAccess the device admin interface or check the firmware version through the system information page or CLI command (typically 'show version' or similar).Affected if The firmware version is below 4.5.0 (e.g., 4.4.x, 4.3.x, etc.)
-
Locate the 'get view' method endpointNavigate to or attempt to access the web endpoint that provides the 'get view' functionality. This is typically found in the RAS web interface under view management or dashboard settings.Affected if The 'get view' method endpoint is accessible and responds to HTTP requests.
-
Inspect the 'view' parameter reflectionSend an HTTP request to the affected endpoint with a test value in the 'view' parameter (e.g., ?view=testvalue) and examine the HTTP response body to see if the value is reflected back without sanitization.Affected if The 'view' parameter value is reflected directly in the HTML response without encoding or sanitization (e.g., <div>testvalue</div> appears verbatim in the response).
If the ETIC RAS firmware version is below 4.5.0 and the 'view' parameter in the 'get view' method reflects user input unencoded in the HTTP response, the environment is affected by CVE-2024-26157.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.5.0
Upgrade to ETIC RAS version 4.5.0 or later; implement proper input validation and output encoding on the 'view' parameter in the affected method.
ETIC Telecom RAS Firmware 4.5.0 or later
- Identify the current firmware version of the ETIC Telecom Remote Access Server by accessing the web interface or checking system information
- Download firmware version 4.5.0 or later from the official ETIC Telecom support portal or vendor distribution channel
- Access the RAS device administrative interface and navigate to the firmware update section
- Upload and apply the firmware version 4.5.0 or later following the vendor's documented upgrade procedure
- After the device restarts, verify the firmware version has been updated to 4.5.0 or later
- Test that the view parameter in the get view method properly sanitizes input and no longer reflects unsanitized data in the HTTP response
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26157 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-26157 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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