Spectra Assure
Community
warningRisk: Vulnerabilities
Scanned: 9 days ago

@esbuild/linux-x64

The Linux 64-bit binary for esbuild, a JavaScript bundler.
License: Permissive (MIT)
Published: over 1 year ago
Visit GitHub
See on npm

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 high severity vulnerabilities
Hardening
1 baseline mitigations missing

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

4.72B
Recorded Downloads Since 2021
2
Contributors
0
Declared Dependencies
32
Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.

Prevalence in npm community

22 packages
found in
Top 100
114 packages
found in
Top 1k
1440 packages
found in
Top 10k
528.88k packages
in community

Next steps

Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

ASLR (address-space layout randomization) is a mitigation technique that increases the difficulty of performing buffer-overflow attacks that require the attacker to know the address of the program in memory. This is done by loading the program at a randomly selected address in the process' address space. ASLR-enabled kernels can choose a random load address only for position-independent executables and code.

Prevalence in npm community

0 packages
found in
Top 100
2 packages
found in
Top 1k
53 packages
found in
Top 10k
8.46k packages
in community

Next steps

To support ASLR, the program must be compiled as position-independent code. In most compilers, this is done by passing the corresponding position-independent flag, such as -fPIC for shared libraries or -fPIE for executables.

Problem

On Linux, external symbols are resolved via the procedure linkage table (PLT) and the global offset table (GOT). The global offset table is split into two tables - one for external data, and one for external functions. Without any protection, both are writable at runtime and thus leave the executable vulnerable to data overwrite attacks and pointer hijacking. Data overwrite attacks can be mitigated by using partial read-only relocations, while pointer hijacking can be mitigated with full read-only relocations. Both approaches have some drawbacks. Partial read-only relocations don't provide full protection, because the external function GOT remains writable. Full read-only relocations require that all external function symbols are resolved at load-time instead of during execution. This may increase loading time for large programs.

Prevalence in npm community

0 packages
found in
Top 100
2 packages
found in
Top 1k
49 packages
found in
Top 10k
6.27k packages
in community

Next steps

In most cases, it's recommended to use full read-only relocations (in GCC: -Wl,-z,relro,-z,now).
If the executable load-time is an issue, you should use partial read-only relocations.

Top behaviors

See all behaviors

Prevalence in npm community

Behavior often found in this community (Common)
4 packages
found in
Top 100
15 packages
found in
Top 1k
281 packages
found in
Top 10k
47.49k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
2 packages
found in
Top 100
9 packages
found in
Top 1k
233 packages
found in
Top 10k
39.73k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
2 packages
found in
Top 1k
57 packages
found in
Top 10k
8.17k packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
1 packages
found in
Top 1k
62 packages
found in
Top 10k
8.07k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
1 packages
found in
Top 100
1 packages
found in
Top 1k
113 packages
found in
Top 10k
18.07k packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(1 Active Vulnerabilities)
1 (1 Fixable)
CVE-2024-24791h
None
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for @esbuild/linux-x64

What is @esbuild/linux-x64?

The Linux 64-bit binary for esbuild, a JavaScript bundler. For more information about this package, visit its homepage.

Is @esbuild/linux-x64 malicious or is it safe to use?

The npm package @esbuild/linux-x64 was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is @esbuild/linux-x64 popular?

The npm package @esbuild/linux-x64 ranks among the top 10000 projects in this community. It has 5B recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure @esbuild/linux-x64 once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how @esbuild/linux-x64 behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a @esbuild/linux-x64 version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.