CVE-2007-0108
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 · uneditednwgina.dll in Novell Client 4.91 SP3 for Windows 2000/XP/2003 does not delete user profiles during a Terminal Service or Citrix session, which allows remote authenticated users to invoke alternate user profiles.
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 confidenceThe nwgina.dll component in Novell Client 4.91 SP3 fails to properly delete user profiles after Terminal Service or Citrix sessions end. This leaves remnant profile data on the system that authenticated remote users can potentially access, leading to information disclosure or privilege escalation via alternate user profiles.
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= 4.91CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/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.
-
Identify Novell Client installation versionCheck the Windows registry at HKLM\SOFTWARE\Novell\Client or look for Novell Client in Add/Remove Programs. Run 'reg query "HKLM\SOFTWARE\Novell" /v Version' if the key exists.Affected if The installed version is exactly 4.91 (or the version cannot be determined but Novell Client 4.91 is present)
-
Verify nwgina.dll component presenceLocate nwgina.dll in the Novell Client installation directory, typically in the system32 folder or Novell program directory. Check file properties for version information.Affected if nwgina.dll exists on the system and is associated with Novell Client 4.91
-
Confirm Terminal Services or Citrix is enabledCheck system services for Remote Desktop Services (Terminal Services) or Citrix services. Query 'reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections' to check if Terminal Services is active.Affected if Terminal Services or Citrix is enabled and users can initiate remote sessions
-
Inspect profile directory for remnant dataExamine the folder C:\Documents and Settings\ (Windows XP/2003) or C:\Users\ (Windows Vista/7/2008) for user profile folders that persist after session termination. Look for profiles not associated with local users.Affected if User profile directories remain after Terminal Service or Citrix sessions end, showing incomplete profile cleanup
-
Check permissions on orphaned profile foldersUse 'icacls' or examine security permissions on leftover profile folders to determine if alternate users can access them. Verify which authenticated users have read or write access.Affected if Authenticated remote users have access to profile directories belonging to other users, indicating improper cleanup
A system is affected if Novell Client 4.91 with nwgina.dll is installed, Terminal Services or Citrix is enabled, and user profile folders persist after session termination with insecure permissions.
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 dataUpgrade to a patched version of Novell Client that addresses this profile cleanup issue, or implement compensatory controls such as forced profile deletion policies and session termination scripts for Terminal Services/Citrix environments.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0108 — 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-2007-0108 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