dbcve.org
Evc04 Configuration InterfaceApplication · Vestel

CVE-2024-8997

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-18
Fix available
A fix is available. Upgrade to after 18.03.2025 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Vestel EVC04 Configuration Interface allows SQL Injection. This issue affects EVC04 Configuration Interface: before V3.187, V4.53.

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 · moderate confidence

A SQL injection vulnerability exists in the Vestel EVC04 Configuration Interface, allowing attackers to inject malicious SQL commands through unsanitized user inputs. The vulnerability affects firmware versions prior to V3.187 and V4.53, with a critical CVSS score of 9.8 indicating potential for complete database compromise and remote code execution.

MitigationUpgrade the EVC04 firmware to version V3.187 or V4.53 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the Configuration Interface and implement input validation at network boundaries.

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
Evc04 Configuration InterfaceApplication
Affected:<= 18.03.2025

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 EVC04 firmware version
    Access the Vestel EVC04 Configuration Interface through its web GUI or via CLI (SSH/Telnet) and locate the firmware version information, usually found in the System Info, Status, or About page.
    Affected if The firmware version is displayed as a date earlier than 18.03.2025, or shows a version below V3.187 or V4.53.
  2. Identify if the Configuration Interface is enabled
    Log into the device admin panel and navigate to Network Settings or Interface Settings. Verify whether the Configuration Interface (web-based management portal) is currently enabled.
    Affected if The Configuration Interface is enabled and accessible on the network.
  3. Confirm the interface is network-exposed
    Check the device's firewall rules or access settings to determine if the Configuration Interface is reachable from external networks or only from a trusted local subnet.
    Affected if The Configuration Interface is reachable from untrusted networks or the internet.
  4. Review input handling in login or query parameters
    If you have access to device logs or can test the interface, observe how the web application handles user input in login fields, search parameters, or other query-enabled endpoints.
    Affected if User inputs are accepted and processed without visible sanitization, or error messages reveal SQL syntax details.

You are affected if your Vestel EVC04 firmware version predates V3.187 or V4.53 (earlier than 18.03.2025) and the Configuration Interface is enabled and network-accessible.

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 a release after 18.03.2025
Interim mitigation

Upgrade the EVC04 firmware to version V3.187 or V4.53 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the Configuration Interface and implement input validation at network boundaries.

Recommended fix High confidence

Upgrade to Vestel EVC04 Configuration Interface V3.187 or V4.53 (or later stable release)

  1. Identify the current version of Vestel EVC04 Configuration Interface by accessing the admin interface or checking system information
  2. If the current version is before V3.187 or V4.53, the system is vulnerable and requires an upgrade
  3. Contact Vestel support or visit the official Vestel website to obtain the fixed version (V3.187 or V4.53 or later)
  4. Backup the current EVC04 Configuration Interface settings and any critical data before performing the upgrade
  5. Apply the upgrade to V3.187 or V4.53 (or later stable release) following the vendor's documented upgrade procedure
  6. After upgrading, verify that the SQL injection vulnerability is resolved by confirming the version number and optionally running vulnerability scans
  7. Restrict network access to the EVC04 Configuration Interface to minimize exposure until the patch is applied
Caveat Review vendor release notes for any configuration or compatibility changes between your current version and the fixed version before upgrading

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

Fix this in Evc04 Configuration Interface Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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