VYPR
Unrated severityNVD Advisory· Published Feb 15, 2018· Updated Sep 16, 2024

CVE-2016-8525

CVE-2016-8525

Description

A path traversal vulnerability in HPE iMC PLAT allows unauthenticated remote attackers to read arbitrary files via the parafile parameter.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A path traversal vulnerability in HPE iMC PLAT allows unauthenticated remote attackers to read arbitrary files via the parafile parameter.

Vulnerability

The vulnerability is a path traversal in the /rptviewer/servlets/redirectviewer servlet of HPE iMC PLAT. The parafile parameter is not properly validated, allowing directory traversal sequences (e.g., ../) to read arbitrary files. Affected versions include HPE iMC PLAT v7.2 E0403P06 and earlier. The issue was resolved in iMC PLAT 7.3 E0504 or later [1].

Exploitation

An unauthenticated attacker can send a crafted HTTP request to the /rptviewer/servlets/redirectviewer endpoint with a parafile parameter containing path traversal sequences. No authentication or special privileges are required. The attacker can read any file on the system that the iMC process has access to [1].

Impact

Successful exploitation leads to remote disclosure of sensitive information, such as configuration files, credentials, or other data. The attacker gains read access to arbitrary files, compromising confidentiality [1].

Mitigation

HPE released iMC PLAT 7.3 E0504 which fixes the issue. Users should upgrade to that version or later. No workaround is mentioned in the available references. The vulnerability is not listed on CISA KEV [1].

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2
  • HPE/iMC PLATllm-fuzzy
    Range: <=7.2 E0403P06
  • Hewlett Packard Enterprise/iMC PLATv5
    Range: v7.2 E0403P06 and earlier

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.