Skip to content
Fencer Intel
high —

GHSA-hfwx-c7q6-g54c json

Vulnerability allowing for reading internal HTTP resources

published 5y ago modified 5y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

The vulnerability allows for reading and outputting files served by other services on the internal network in which the export server is hosted. If the export server is exposed to the internet, this potentially allows a malicious user to gain read access to internal web-resources.

The impact is limited to internal services that serve content via. HTTP(S), and requires the attacker to know internal hostnames/IP addresses.

The previous versions have been marked as deprecated on NPM.

### Patches

Version 2.1.0 released alongside this security advisory addresses the issue. **Please note that this release is not backwards compatible out of the box. See the [changelog](https://github.com/highcharts/node-export-server/blob/master/CHANGELOG.md) for details.**

Additionally, it's also recommended to upgrade to the latest version of Highcharts to get the added input sanitation implemented in version 9.0 and later.

### Workarounds

There are no known workarounds to the issue - an upgrade to version 2.1.0 is required.

### For more information If you have any questions or comments about this advisory: * Open an issue in [the export server issue tracker](https://github.com/highcharts/node-export-server/issues) * Email us at [security@highsoft.com](mailto:security@highsoft.com)

Patch / fix

  • npm highcharts-export-server 2.1.0

Is GHSA-hfwx-c7q6-g54c in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm highcharts-export-server
<2.1.0
2.1.0

Classification

Weakness
  • CWE-552 Files or Directories Accessible to External Parties

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.