dbcve.org
Access ManagerApplication · Novell

CVE-2010-0284

HIGH · 10.0 CVSS v2.0 Published 2010-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Directory traversal vulnerability in the getEntry method in the PortalModuleInstallManager component in a servlet in nps.jar in the Administration Console (aka Access Management Console) in Novell Access Manager 3.1 before 3.1.2-281 on Windows allows remote attackers to create arbitrary files with any contents, and consequently execute arbitrary code, via a .. (dot dot) in a parameter, aka ZDI-CAN-678.

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 confidence

Directory traversal vulnerability in the getEntry method of the PortalModuleInstallManager component in the Administration Console servlet (nps.jar) of Novell Access Manager 3.1 on Windows allows remote attackers to inject path traversal sequences (..) into a parameter, enabling creation of arbitrary files with attacker-controlled contents and resulting in remote code execution.

MitigationUpgrade Novell Access Manager to version 3.1.2-281 or later. If upgrading is not immediately feasible, restrict network access to the Administration Console and disable the PortalModuleInstallManager component if not required.

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
Access ManagerApplication
Affected:= 3.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Novell Access Manager version
    Locate and inspect the version information for the Novell Access Manager installation. Check installation directories, version files, or admin interfaces for the exact version number (e.g., 3.1, 3.1.1, 3.1.2-281). Compare against the affected version = 3.1.
    Affected if The installed version is exactly 3.1 (any patch level below 3.1.2-281).
  2. Confirm Windows platform
    Verify the operating system where Novell Access Manager is deployed. This vulnerability specifically affects the Windows implementation.
    Affected if Novell Access Manager 3.1 is running on Windows.
  3. Verify Administration Console accessibility
    Determine if the Administration Console servlet (nps.jar) is accessible. Check if the admin interface or associated endpoints are reachable over the network.
    Affected if The Administration Console is accessible (internally or externally).
  4. Confirm PortalModuleInstallManager component status
    Inspect whether the PortalModuleInstallManager component is loaded and active within the Administration Console. Check the servlet configuration and deployed JAR files.
    Affected if The PortalModuleInstallManager component is enabled and loaded by the system.
  5. Check for nps.jar presence
    Locate the nps.jar file in the Administration Console deployment directory. This JAR contains the vulnerable PortalModuleInstallManager component.
    Affected if The nps.jar file is present in the Administration Console installation.

A system is affected if it runs Novell Access Manager version 3.1 on Windows with the Administration Console and PortalModuleInstallManager component accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Novell Access Manager to version 3.1.2-281 or later. If upgrading is not immediately feasible, restrict network access to the Administration Console and disable the PortalModuleInstallManager component if not required.

Recommended fix High confidence

Novell Access Manager 3.1.2-281 or later

  1. 1. Identify the current version of Novell Access Manager 3.1 Administration Console installed on the Windows system
  2. 2. If the version is earlier than 3.1.2-281, plan an upgrade to version 3.1.2-281 or later
  3. 3. Before upgrading, perform a complete backup of the Access Manager configuration and data
  4. 4. Apply the upgrade to the Administration Console (Access Management Console) component
  5. 5. After upgrade, verify that the getEntry method in PortalModuleInstallManager no longer accepts directory traversal sequences (..) in parameters
  6. 6. Test that normal administrative functions still work as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0284 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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