CVE-2009-1628
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 · uneditedStack-based buffer overflow in mnet.exe in Unisys Business Information Server (BIS) 10 and 10.1 on Windows allows remote attackers to execute arbitrary code via a crafted TCP packet.
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 confidenceStack-based buffer overflow in mnet.exe in Unisys Business Information Server (BIS) versions 10 and 10.1 on Windows allows remote attackers to execute arbitrary code via a crafted TCP packet to the BIS 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= 10= 10.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Unisys BIS installationCheck for Unisys Business Information Server in Windows Programs and Features (Add/Remove Programs), or look for the installation directory (commonly under C:\Program Files\Unisys\BIS or similar).Affected if Unisys Business Information Server is installed on the system
-
Confirm the installed versionRight-click on the mnet.exe executable (typically in the BIS bin directory), select Properties, and check the Version tab. Alternatively, check the version in Programs and Features.Affected if The installed version is 10 or 10.1
-
Verify mnet.exe is presentLocate the mnet.exe file in the BIS installation directory. Check if the file exists on the system.Affected if mnet.exe exists in the BIS installation folder
-
Check if BIS service is runningOpen Task Manager or use 'sc query' command to check if the BIS service (mnet) is currently running.Affected if The mnet.exe process or BIS service is actively running
-
Assess network exposureUse 'netstat -an' or a port scanner to determine if the BIS service is listening on any TCP ports and if it is accessible from the network.Affected if The BIS service is listening on a TCP port and is reachable from untrusted networks
You are affected if Unisys Business Information Server versions 10 or 10.1 is installed, mnet.exe is present, and the service is running and accessible 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 dataApply vendor patches if available; if no patch exists, restrict network access to the BIS service via firewall and consider disabling the mnet.exe service until remediation is possible.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1628 — 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-2009-1628 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