What is the severity of CVE-2003-0641?

CVE-2003-0641 has been classified as a high severity vulnerability due to its potential for local users to inject arbitrary modules.

How do I fix CVE-2003-0641?

To mitigate CVE-2003-0641, it is recommended to upgrade to WatchGuard ServerLock version 2.0.3 or later.

What type of attack does CVE-2003-0641 allow?

CVE-2003-0641 allows local users to perform DLL injection and API hooking attacks.

Who is affected by CVE-2003-0641?

CVE-2003-0641 affects users of WatchGuard ServerLock versions 2.0, 2.0.1, and 2.0.2 on Windows 2000.

What is the impact of CVE-2003-0641?

The impact of CVE-2003-0641 includes unauthorized execution of code and potential escalation of user privileges.

Vulnerability/
CVE-2003-0641

medium

4.6

CWE

NVD-CWE-Other

2/8/2003

8/8/2024

CVE-2003-0641

First published: Sat Aug 02 2003(Updated: )

WatchGuard ServerLock for Windows 2000 before SL 2.0.3 allows local users to load arbitrary modules via the OpenProcess() function, as demonstrated using (1) a DLL injection attack, (2) ZwSetSystemInformation, and (3) API hooking in OpenProcess.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
WatchGuard ServerLock	=2.0
WatchGuard ServerLock	=2.0.1
WatchGuard ServerLock	=2.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2003-0641?
CVE-2003-0641 has been classified as a high severity vulnerability due to its potential for local users to inject arbitrary modules.
How do I fix CVE-2003-0641?
To mitigate CVE-2003-0641, it is recommended to upgrade to WatchGuard ServerLock version 2.0.3 or later.
What type of attack does CVE-2003-0641 allow?
CVE-2003-0641 allows local users to perform DLL injection and API hooking attacks.
Who is affected by CVE-2003-0641?
CVE-2003-0641 affects users of WatchGuard ServerLock versions 2.0, 2.0.1, and 2.0.2 on Windows 2000.
What is the impact of CVE-2003-0641?
The impact of CVE-2003-0641 includes unauthorized execution of code and potential escalation of user privileges.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/references
agent/weakness
agent/last-modified-date
agent/tags
agent/first-publish-date
agent/event
agent/description
agent/source
vendor/watchguard
canonical/watchguard serverlock
version/watchguard serverlock/2.0
version/watchguard serverlock/2.0.1
version/watchguard serverlock/2.0.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2003-0641?
CVE-2003-0641 has been classified as a high severity vulnerability due to its potential for local users to inject arbitrary modules.
How do I fix CVE-2003-0641?
To mitigate CVE-2003-0641, it is recommended to upgrade to WatchGuard ServerLock version 2.0.3 or later.
What type of attack does CVE-2003-0641 allow?
CVE-2003-0641 allows local users to perform DLL injection and API hooking attacks.
Who is affected by CVE-2003-0641?
CVE-2003-0641 affects users of WatchGuard ServerLock versions 2.0, 2.0.1, and 2.0.2 on Windows 2000.
What is the impact of CVE-2003-0641?
The impact of CVE-2003-0641 includes unauthorized execution of code and potential escalation of user privileges.