Cyber Resilience

CVE-2025-37097

Hpe Insight Remote Support ≤ 7.15.0.646

Public PoC
Published
01 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0047 39th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2025-37097 is a high-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Hpe Insight Remote Support. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability in HPE Insight Remote Support (IRS) prior to v7.15.0.646 may allow an unauthenticated denial of service

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-37098Same product: Hpe Insight Remote Support
CVE-2024-53673Same product: Hpe Insight Remote Support
CVE-2024-11622Same product: Hpe Insight Remote Support
CVE-2024-53675Same product: Hpe Insight Remote Support
CVE-2024-53674Same product: Hpe Insight Remote Support
CVE-2025-37099Same product: Hpe Insight Remote Support
CVE-2024-53676Same product: Hpe Insight Remote Support
CVE-2023-30904Same product: Hpe Insight Remote Support
CVE-2025-37095Same vendor: Hpe
CVE-2025-37090Same vendor: Hpe

Affected Assets

hpe
insight remote support
≤ 7.15.0.646

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V8.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement directly stops unauthorized callers from invoking dangerous API methods or functions.

Least privilege restricts which users or processes may reach dangerous methods, limiting exposure.

Least functionality removes or disables non-essential dangerous methods from the exposed interface altogether.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.

PR.PS-06 mostly match
prevents

Secure SDLC practices stop developers from exposing dangerous functions in the first place.

ID.RA-01 partial match
prevents

Vulnerability identification processes will surface exposed dangerous methods during assessment.

PR.IR-01 partial match
prevents

Logical access controls at the network/environment layer can limit reachability of exposed functions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect exposed dangerous functions, but does not prevent their initial introduction.

degrades

Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.

prevents

Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.

prevents

Secure development life cycle requires removal or protection of dangerous APIs during design and coding.

prevents

Application security requirements can mandate that dangerous methods are not exposed in interfaces.

prevents

Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Ubuntu 22.04 (3 rules)
  • V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749
  • V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-749
  • V-260557 Ubuntu 22.04 LTS must be configured to use AppArmor. prevents CWE-749
Ubuntu 24.04 (1 rule)
  • V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749

References