Open Enterprise ServerApplication · Novell

CVE-2017-5182

HIGH · 7.5 CVSS v3.0 Published 2017-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Remote Manager in Open Enterprise Server (OES) allows unauthenticated remote attackers to read any arbitrary file, via a specially crafted URL, that allows complete directory traversal and total information disclosure. This vulnerability is present on all versions of OES for linux, it applies to OES2015 SP1 before Maintenance Update 11080, OES2015 before Maintenance Update 11079, OES11 SP3 before Maintenance Update 11078, OES11 SP2 before Maintenance Update 11077).

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

Open Enterprise Server Remote Manager contains a directory traversal vulnerability that allows unauthenticated remote attackers to read arbitrary files on the system via specially crafted URLs. This affects all OES for Linux versions prior to the specified maintenance updates, enabling complete information disclosure including sensitive configuration files, credentials, or system data.

MitigationApply the appropriate maintenance update for the affected OES version (MU11080 for OES2015 SP1, MU11079 for OES2015, MU11078 for OES11 SP3, MU11077 for OES11 SP2) to patch the Remote Manager directory traversal vulnerability.

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 ServerApplication
Affected:= 2.0= 2015= 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

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

  1. Identify Open Enterprise Server installation and version
    Run 'rpm -qa | grep -i oes' or check /etc/novell-release for OES version information. Compare the installed version against the affected versions: OES 2.0, OES 2015, or OES 11.0.
    Affected if The installed OES version is 2.0, 2015, or 11.0 without the corresponding maintenance update (MU11080, MU11079, MU11078, or MU11077).
  2. Verify Remote Manager service status
    Check if the Remote Manager service (novell-nrm or httpd-novell-remote-manager) is running. Run 'rcnovell-nrm status' or check the process list for the Remote Manager daemon.
    Affected if Remote Manager service is running and exposed to network access.
  3. Confirm Remote Manager web interface accessibility
    Attempt to access the Remote Manager web interface via HTTP/HTTPS on port 8009 (default OES Remote Manager port). Use a test request such as 'curl http://localhost:8009/' to verify the service is listening.
    Affected if Remote Manager web interface responds to requests, indicating the vulnerable component is network-accessible.
  4. Test for directory traversal vulnerability
    Send a crafted request to read a known file via directory traversal, such as: 'curl http://<server>:8009/../../../../../../../../../../etc/passwd' or similar path traversal pattern.
    Affected if The server returns file contents from outside the web root, confirming the directory traversal vulnerability is present.

A system is affected if it runs OES 2.0, OES 2015, or OES 11.0 with Remote Manager enabled and accessible, and the directory traversal test successfully reads arbitrary files.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate maintenance update for the affected OES version (MU11080 for OES2015 SP1, MU11079 for OES2015, MU11078 for OES11 SP3, MU11077 for OES11 SP2) to patch the Remote Manager directory traversal vulnerability.

Fix this in Open Enterprise Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5182 — 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-2017-5182 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