dbcve.org
MoviconApplication · Progea

CVE-2011-2963

HIGH · 10.0 CVSS v2.0 Published 2011-07-29
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
TCPUploadServer.exe in Progea Movicon 11.2 before Build 1084 does not require authentication for critical functions, which allows remote attackers to obtain sensitive information, delete files, execute arbitrary programs, or cause a denial of service (crash) via a crafted packet to TCP port 10651.

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

TCPUploadServer.exe in Progea Movicon 11.2 before Build 1084 lacks authentication on critical functions, allowing unauthenticated remote attackers to send crafted packets to TCP port 10651 to obtain sensitive information, delete files, execute arbitrary programs, or cause denial of service.

MitigationUpgrade Movicon to Build 1084 or later. If upgrading is immediately infeasible, restrict network access to TCP port 10651 using firewalls or network segmentation to prevent untrusted external access to the vulnerable service.

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
MoviconApplication
Affected:= 11.2

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

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

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 Movicon 11.2 installation
    Check installed programs list or common installation directories for Progea Movicon version 11.2. Look for executable files named TCPUploadServer.exe in the Movicon installation folder.
    Affected if Movicon 11.2 is installed and TCPUploadServer.exe exists on the system
  2. Verify the build version
    Right-click on TCPUploadServer.exe, select Properties, then view the Details tab to check the File Version or Product Version. Alternatively, check the About or Version information within the Movicon application.
    Affected if The build version is earlier than Build 1084 (versions like 11.2.0 through 11.2.x with build numbers below 1084)
  3. Check if TCPUploadServer.exe is running
    Open Task Manager or use command 'tasklist /FI "IMAGENAME eq TCPUploadServer.exe"' to see if the process is active.
    Affected if TCPUploadServer.exe process is currently running on the system
  4. Detect if TCP port 10651 is open
    Run 'netstat -an | findstr :10651' or use a port scanner to check if TCP port 10651 is listening. Verify the listening address (0.0.0.0 indicates exposed network access).
    Affected if TCP port 10651 is open and listening, especially on all network interfaces (0.0.0.0) rather than localhost only

A system is affected if Progea Movicon 11.2 with TCPUploadServer.exe is installed with a build version earlier than 1084, the process is running, and TCP port 10651 is exposed on the network.

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
Patch available Apply the vendor patch
Vendor patch www.us-cert.gov →
Interim mitigation

Upgrade Movicon to Build 1084 or later. If upgrading is immediately infeasible, restrict network access to TCP port 10651 using firewalls or network segmentation to prevent untrusted external access to the vulnerable service.

Recommended fix High confidence

Movicon 11.2 Build 1084 or later

  1. Identify the current Movicon version by checking About or version information in the application
  2. Download Movicon 11.2 Build 1084 or later from the vendor's official distribution channels
  3. Before upgrading, backup all existing project files, configurations, and runtime data
  4. If possible, test the upgrade in a non-production environment first
  5. Run the installer for Movicon 11.2 Build 1084 or later
  6. After upgrading, verify that TCPUploadServer.exe is updated and the new version is running
  7. Confirm that authentication is now required for TCPUploadServer.exe operations on TCP port 10651
  8. Test critical operations (file access, program execution) to ensure proper authentication is enforced

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

Fix this in Movicon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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