CVE-2005-1907
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 ISA Firewall service in Microsoft Internet Security and Acceleration (ISA) Server 2000 allows remote attackers to cause a denial of service (Wspsrv.exe crash) via a large amount of SecureNAT network traffic.
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 confidenceThis is a denial of service vulnerability in Microsoft ISA Server 2000's Firewall service. Remote attackers can crash the Wspsrv.exe process by sending a large volume of SecureNAT network traffic, causing the firewall service to become unavailable.
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= 2000CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ISA Server 2000 is installedCheck Add/Remove Programs for Microsoft ISA Server 2000, or locate the ISA installation directory (typically C:\Program Files\Microsoft ISA Server) and verify the version from isaserver.exe or isauir.dll propertiesAffected if ISA Server 2000 is present on the system
-
Verify Firewall service is runningOpen Task Manager or run 'tasklist /svc' and look for the Wspsrv.exe process (Firewall service), or check Services console for the Microsoft Firewall serviceAffected if Wspsrv.exe process is running (the vulnerability crashes this service)
-
Check if SecureNAT is enabledOpen ISA Server Management, expand the server node, click on Networks, then inspect the SecureNAT clients configuration, or check the isa.xml configuration file for SecureNAT client rulesAffected if SecureNAT clients are configured and enabled (this is the attack vector for the DoS)
The system is affected if ISA Server 2000 is installed, the Firewall service (Wspsrv.exe) is running, and SecureNAT clients are enabled, as the DoS vulnerability is triggered by excessive SecureNAT traffic crashing the firewall service.
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 dataSince ISA Server 2000 is end-of-life and no longer supported, the primary remediation is to migrate to a supported firewall solution (such as Microsoft Forefront TMG or third-party alternatives). If immediate migration is not feasible, implement network-level filtering to restrict unauthorized traffic and consider rate limiting on perimeter devices.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1907 — 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-1907 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