dbcve.org
EoscadaApplication · C3 Ilex

CVE-2012-1810

MEDIUM · 5.0 CVSS v2.0 Published 2012-11-13
Fix available
A fix is available. Upgrade to after 11.0.19.1 or later.
See remediation →
59/100
Remediation priority · Elevated
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
EOSCoreScada.exe in C3-ilex EOScada before 11.0.19.2 allows remote attackers to cause a denial of service (daemon restart) by sending data to TCP port (1) 5050 or (2) 24004.

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

EOSCoreScada.exe in C3-ilex EOScada versions prior to 11.0.19.2 contains a denial of service vulnerability where sending specially crafted data to TCP ports 5050 or 24004 causes the daemon to restart unexpectedly.

MitigationUpgrade C3-ilex EOScada to version 11.0.19.2 or later to patch the vulnerability. If immediate patching is not possible, consider network segmentation or firewall rules to restrict untrusted access to ports 5050 and 24004.

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
EoscadaApplication
Affected:<= 11.0.19.1

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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. Locate EOSCoreScada.exe process
    Open Task Manager or use command 'tasklist /FI "IMAGENAME eq EOSCoreScada.exe"' to find if the EOSCoreScada.exe process is running on the system
    Affected if The process is running and the software version is 11.0.19.1 or earlier
  2. Identify installed EOScada version
    Check the program's version information: right-click EOSCoreScada.exe in the installation directory, select Properties, then look at the Details tab for the Version field, or use 'wmic product get name,version' if available
    Affected if The displayed version is 11.0.19.1 or lower (any version below 11.0.19.2)
  3. Verify listening network ports
    Run 'netstat -an | findstr "5050\|24004"' or use PowerShell 'Get-NetTCPConnection -LocalPort 5050,24004' to check if TCP ports 5050 or 24004 are in LISTENING state
    Affected if Either port 5050 or 24004 is open and listening, and the software version is 11.0.19.1 or earlier

You are affected if C3-ilex EOScada version 11.0.19.1 or earlier is installed and the EOSCoreScada.exe service is running with TCP ports 5050 or 24004 exposed.

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
Upgrade available Upgrade to a release after 11.0.19.1
Interim mitigation

Upgrade C3-ilex EOScada to version 11.0.19.2 or later to patch the vulnerability. If immediate patching is not possible, consider network segmentation or firewall rules to restrict untrusted access to ports 5050 and 24004.

Fix this in Eoscada Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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