How severe is GHSA-hp5f-qqrw-c8gj?

No CVSS score has been assigned to GHSA-hp5f-qqrw-c8gj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hp5f-qqrw-c8gj?

GHSA-hp5f-qqrw-c8gj affects the following packages: kibana (npm). Ecosystems affected: npm.

How do I fix GHSA-hp5f-qqrw-c8gj?

Update kibana to 7.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hp5f-qqrw-c8gj is resolved across your whole dependency graph.

How do I detect GHSA-hp5f-qqrw-c8gj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kibana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hp5f-qqrw-c8gj if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-hp5f-qqrw-c8gj actively exploited in the wild?

No public exploit code has been indexed for GHSA-hp5f-qqrw-c8gj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hp5f-qqrw-c8gj?

GHSA-hp5f-qqrw-c8gj has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hp5f-qqrw-c8gj?

GHSA-hp5f-qqrw-c8gj is classified as Information Exposure (CWE-200), CWE-319 (CWE-319). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hp5f-qqrw-c8gj published, and has it been updated?

GHSA-hp5f-qqrw-c8gj was published on May 24, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Kibana Sensitive Data Disclosure

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

kibananpm

118downloads / week

Description

It was discovered that Kibana’s JIRA connector & IBM Resilient connector could be used to return HTTP response data on internal hosts, which may be intentionally hidden from public view. Using this vulnerability, a malicious user with the ability to create connectors, could utilize these connectors to view limited HTTP response data on hosts accessible to the cluster.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`kibana`	≥ 7.8.0&&< 7.15.2	7.15.2`npm install kibana@7.15.2`

Affected Products

1 product · 1 configurations

Application

kibanaelastic

≥ 7.8.0 && < 7.15.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kibana, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kibana to 7.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hp5f-qqrw-c8gj is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

It was discovered that Kibana’s JIRA connector & IBM Resilient connector could be used to return HTTP response data on internal hosts, which may be intentionally hidden from public view. Using this vulnerability, a malicious user with the ability to create connectors, could utilize these connectors to view limited HTTP response data on hosts accessible to the cluster.

O3 Security · Impact-Aware SCA

Is GHSA-hp5f-qqrw-c8gj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

Kibana Sensitive Data DisclosureGHSA-hp5f-qqrw-c8gj