CVE-2005-4812
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 · uneditedThe SISCO OSI stack for Windows, as used by MMS-EASE 7.10 and earlier, AX-S4 MMS 5.01 and earlier, AX-S4 ICCP 3.0103 and earlier, and the ICCP Toolkit for MMS-EASE 4.10 and earlier, allows remote attackers to cause a denial of service (process crash) via certain network traffic, as demonstrated using a Nessus scan.
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 SISCO OSI stack for Windows contains a denial of service vulnerability affecting multiple products (MMS-EASE, AX-S4 MMS, AX-S4 ICCP, and ICCP Toolkit). Remote attackers can send specially crafted network traffic to crash the affected process, as demonstrated by Nessus vulnerability scanning.
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<= 3.0103<= 5.01<= 4.10<= 7.10CVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SISCO productsCheck Windows installed programs list or running processes for MMS-EASE, AX-S4 MMS, AX-S4 ICCP, or ICCP Toolkit. Look for process names like 'axs4icc.exe', 'axs4mms.exe', 'mmsease.exe', or 'iccptoolkit.exe'.Affected if Any of the four affected products are installed on the system
-
Check installed version numbersLocate the version information for the installed SISCO product through its About dialog, help menu, or program files directory. Common locations include the executable file properties or a 'version.txt' file in the installation folder.Affected if The installed version is at or below 3.0103 for AX-S4 ICCP, 5.01 for AX-S4 MMS, 4.10 for ICCP Toolkit, or 7.10 for MMS-EASE
-
Identify running SISCO servicesOpen Windows Task Manager or use 'netstat -ano' command to identify processes listening on network ports. SISCO OSI stack typically uses ports associated with MMS (ISO 9506) or ICCP (IEC 60870-6) protocols.Affected if A SISCO product process is running and actively listening on any network port
-
Determine network exposureReview firewall rules and network configuration to determine if the affected system is accessible from untrusted networks. Check if the SISCO service port is bound to a public or routable IP address versus localhost only.Affected if The system is directly accessible from network and the vulnerable service is listening on an exposed IP address
A user is affected if any of the four SISCO products is installed with a version at or below the specified thresholds and the service is running and network-accessible.
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 dataApply vendor patches or updates from SISCO for the OSI stack; if patches are unavailable, implement network segmentation and firewall rules to restrict untrusted network access to affected systems.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4812 — 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-2005-4812 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