CVE-2005-0746
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 Mini FTP server in Novell iChain 2.2 and 2.3 SP2 and earlier allows remote unauthenticated attackers to obtain the full path of the server via the PWD command.
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 Mini FTP server in Novell iChain 2.2 and 2.3 SP2 and earlier contains an information disclosure vulnerability. The PWD (Print Working Directory) command, which should return only the current directory name, instead returns the full server filesystem path to any unauthenticated remote attacker. This reveals internal path structures that can aid in reconnaissance for more sophisticated attacks.
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= 2.2= 2.2.113= 2.3CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 iChain installationLocate the Novell iChain installation directory, typically under C:\Novell\iChain or /opt/novell/ichain. Check for the presence of iChain installation files or check Windows services for 'Novell iChain' services.Affected if Novell iChain is not installed or the installation cannot be found.
-
Determine installed iChain versionCheck the version of Novell iChain by viewing version information in the Windows 'Add/Remove Programs' dialog, or check the icversion.txt or version.ini file in the iChain installation directory.Affected if The installed version is 2.2, 2.2.113, or 2.3 (or any version prior to 2.3 SP2). Compare your version to these affected ranges.
-
Verify Mini FTP server is enabledCheck the iChain administration console or configuration files for the Mini FTP server status. Look for FTP-related settings in the iChain configuration or check if FTP service/port (port 21) is listening.Affected if The Mini FTP server is enabled and FTP port 21 is listening/open to network access.
-
Confirm network accessibility of FTP serviceFrom an external or non-privileged network perspective, attempt to verify if port 21 is accessible or check firewall rules that allow inbound FTP connections to the iChain server.Affected if The FTP service is accessible from untrusted networks or the vulnerability is exposed to unauthenticated remote attackers.
A user is affected if Novell iChain version 2.2, 2.2.113, or 2.3 is installed, the Mini FTP server is enabled, and the FTP service is network-accessible to unauthenticated remote attackers who could issue PWD commands to disclose server filesystem 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 dataUpgrade to a patched version of Novell iChain or disable the Mini FTP server if not required. If upgrading is not possible, implement network segmentation to restrict FTP access to trusted internal networks only.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0746 — 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-0746 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