# HPE closed a security vulnerability case for StoreOnce Catalyst OST Plug-in without providing any technical explanation. Is this normal? — retained record

> Retained reddit record from reddit:sysadmin.

Canonical: https://highsignal.app/data/records/d49f50b1fbc651e9

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:sysadmin)  published 2026-10-31 18:36 ingested 2026-11-01 02:39

[original source ↗](https://www.reddit.com/r/sysadmin/comments/1xkhtn2/hpe_closed_a_security_vulnerability_case_for/)

## retained text



```
I would like to share an experience with HPE Support and get feedback from other infrastructure engineers.

We identified a security finding on several Veritas NetBackup Media Servers running the HPE StoreOnce Catalyst OST Plug-in (version 4.4.0).

A credentialed Nessus scan detected an outdated Java runtime bundled within the plug-in installation directory:

* Detected Java version: [8.0.161.12](http://8.0.161.12) (build 8.0.161)
* Nessus Plugin ID: 154345
* Severity: High (CVSS 7.5)
* Related vulnerabilities: Multiple Oracle Java CVEs from October 2021
* Nessus-reported fixed version: 8.0.311 or later

This was not a generic network scan. It was an authenticated local security assessment.

I opened a support case with HPE. Their support team requested technical details, scan methodology, software versions and diagnostic logs. I provided all requested information.

The case was escalated to Level 2 engineering, so I expected a technical assessment and, hopefully, guidance on a supported remediation path.

Instead, HPE requested Proof of Purchase (POP) and a professional email address.

I explained that I was acting as a service engineer supporting the customer and that the reported issue concerned a software component distributed for use with HPE StoreOnce, not a hardware failure.

I also asked whether the issue could be referred to the relevant product engineering or Product Security team if it was outside the scope of standard hardware support.

Eventually, HPE simply closed the case.

No technical conclusion.  
No confirmation or rejection of the vulnerability finding.  
No information about a fixed plug-in release.  
No remediation recommendations.  
No explanation for closing the case.

I understand that hardware support contracts and entitlement verification exist for a reason. I am not asking HPE to provide free hardware maintenance.

However, I find it difficult to understand why a potential security vulnerability in a software component distributed within the HPE ecosystem cannot even receive a technical assessment or an official recommendation.

**I have a few questions for the community:**

1. Has anyone encountered this particular Java runtime bundled with the HPE StoreOnce Catalyst OST Plug-in?
2. Is there a newer plug-in release with an updated Java runtime?
3. Has anyone successfully obtained security-related assistance from HPE without an active hardware support contract?
4. Is there a separate HPE Product Security escalation process for vulnerabilities in distributed software components?

I would genuinely appreciate feedback from HPE engineers, StoreOnce specialists and anyone who has dealt with a similar situation.

I am primarily interested in finding a technically correct and officially supported way to address this issue.
```



document fetched 2026-11-01 00:33 · canonical https://reddit.com/r/sysadmin/comments/1xkhtn2/hpe_closed_a_security_vulnerability_case_for
