CVE-2007-2950
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 · uneditedCentennial Discovery 2006 Feature Pack 1, which is used by (1) Numara Asset Manager 8.0 and (2) Symantec Discovery 6.5, uses insecure permissions on certain directories, which allows local users to gain privileges.
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 confidenceCentennial Discovery 2006 Feature Pack 1 (used by Numara Asset Manager 8.0 and Symantec Discovery 6.5) contains insecure file system permissions on certain directories, allowing unprivileged local users to modify executable paths or inject malicious code and escalate to higher privileges.
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= 2006_featurepack1= 8.0= 6.5CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Identify installed productCheck if Centennial Discovery 2006 Feature Pack 1, Numara Asset Manager 8.0, or Symantec Discovery 6.5 is installed on the system. Look in Add/Remove Programs (Windows) or check for the product in /opt or Program Files directories.Affected if Any of these three specific versions are installed on the system.
-
Locate application installation directoryFind the installation path for the identified product. Common locations include C:\Program Files\Centennial Discovery, C:\Program Files\Numara, or C:\Program Files\Symantec Discovery. Use registry keys or package management tools if available.Affected if The product is installed and the directory exists on the system.
-
Check permissions on executable directoriesReview file system permissions on directories that contain executable files (.exe, .dll, .bat, .cmd) for the installed product. Use 'icacls' on Windows or 'ls -la' on Unix-like systems to list permissions.Affected if Non-administrative or unprivileged users have Write or Modify permissions on directories containing application executables.
-
Verify executable path integrityInspect configuration files, scripts, or registry entries that define executable paths for the application. Check if these paths point to locations writable by non-admin users.Affected if Executable paths can be modified by unprivileged users, or configuration files are writable by non-admin accounts.
The environment is affected if any of the three specific product versions are installed AND unprivileged users have write access to directories containing application executables or configuration files that define executable paths.
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 dataRestrict permissions on vulnerable directories to prevent unauthorized user write access, or apply vendor patches if available. Verify that only trusted administrators can modify application directories and executable locations.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2950 — 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-2950 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