Open Enterprise ServerOperating system · Novell

CVE-2014-0598

HIGH · 10.0 CVSS v2.0 Published 2014-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 iPrint in Novell Open Enterprise Server (OES) 11 SP1 before Maintenance Update 9151 on Linux has unspecified impact and remote attack vectors.

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 · moderate confidence

Directory traversal vulnerability in Novell iPrint allows remote attackers to access files outside the web root via '../' path manipulation sequences, potentially leading to unauthorized file read/write on the underlying Linux system.

MitigationApply Novell OES 11 SP1 Maintenance Update 9151 or later. If immediate patching is not feasible, restrict network access to iPrint services and monitor for anomalous path traversal patterns in HTTP requests.

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
Open Enterprise ServerOperating system
Affected:= 11.0

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. Identify if Novell Open Enterprise Server is installed
    Check the installed OES version by running 'cat /etc/novell-release' or 'rpm -qi oes-installed' if using RPM-based Linux, or checking the system information panel in iManager
    Affected if The installed version is exactly 11.0 (without service pack updates)
  2. Confirm iPrint module is enabled
    In Novell iManager, navigate to iPrint > Manage Print Manager and verify the iPrint service is listed as active, or run 'rcniprint status' on the OES server
    Affected if iPrint is installed and the service is running (the vulnerability only applies when iPrint is active)
  3. Verify iPrint is exposed to network access
    Check if the iPrint HTTP service (typically port 631) is listening on external interfaces by running 'netstat -an | grep 631' or 'ss -tlnp | grep 631'
    Affected if Port 631 is bound to 0.0.0.0 or an external IP address rather than only localhost (127.0.0.1)
  4. Review HTTP access logs for path traversal attempts
    Examine iPrint HTTP access logs (typically in /var/log/nici/ or /var/log/print/) for requests containing '../' patterns such as '../../../etc/passwd'

You are affected if Novell Open Enterprise Server 11.0 is running with iPrint enabled and exposed to network access, particularly if version shows exactly 11.0 without SP1 or later updates.

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

Apply Novell OES 11 SP1 Maintenance Update 9151 or later. If immediate patching is not feasible, restrict network access to iPrint services and monitor for anomalous path traversal patterns in HTTP requests.

Recommended fix Moderate confidence

Novell Open Enterprise Server 11 SP1 Maintenance Update 9151

  1. Check the current iPrint or OES version: rpm -qi iprint or cat /etc/novell-release
  2. Download Maintenance Update 9151 from Novell Customer Center (https://download.novell.com)
  3. Apply the update using zypper patch or yast online_update depending on the system
  4. Verify the patch was applied successfully: rpm -qi iprint and confirm version reflects the fixed release
  5. Restart the iPrint service: rcnovell-ipsmd restart or systemctl restart novell-ipsmd
Caveat Standard OES maintenance update; test in non-production environment first

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

Fix this in Open Enterprise Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0598 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0598 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