CVE-2014-0778
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 · uneditedTCPUploader module listens on Port 10651/TCP for incoming connections. Exploitation of this vulnerability could allow a remote unauthenticated user access to release OS version information. While this is a minor vulnerability, it represents a method for further network reconnaissance.
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 confidenceThe TCPUploader module listens on port 10651/TCP and exposes OS version information to remote unauthenticated attackers. This information disclosure vulnerability enables further network reconnaissance despite its moderate CVSS score.
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= 11.4CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 Progea Movicon installationCheck for Progea Movicon in installed programs (Windows: Add/Remove Programs, Program Files directory) or check registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Movicon entryAffected if Progea Movicon version 11.4 is installed
-
Verify exact version numberLocate the Movicon executable or check version via file properties, or query the application if accessibleAffected if Installed version equals 11.4 exactly (version 11.4.0 or 11.4.x)
-
Check if TCPUploader module is activeInspect Movicon configuration files or service settings for TCPUploader module status, or check if the module is loaded in running processesAffected if TCPUploader module is enabled or loaded in the Movicon installation
-
Verify port 10651/TCP is listeningRun 'netstat -an | findstr 10651' or use port scanner against localhost to check if port 10651 is in LISTENING stateAffected if Port 10651/TCP is open and listening on any interface (0.0.0.0 or externally accessible)
-
Confirm network exposureCheck firewall rules and binding configuration to determine if port 10651 is accessible from remote systems (not localhost-only)Affected if Port 10651 is bound to non-loopback interface or firewall permits external access to port 10651
User is affected if Progea Movicon version 11.4 is installed with TCPUploader module enabled and port 10651/TCP is exposed on the network.
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.
From vendor dataRestrict access to port 10651/TCP through firewall rules or network segmentation, and disable the TCPUploader module if not required.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0778 — 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-2014-0778 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