Spectra Assure
Community
Docs
failRisk: Vulnerabilities
Scanned: about 20 hours ago

Java

Artifact:
latest
Top 1k
Java Platform Extension for Visual Studio Code
License: Permissive (Apache-2.0)
Published: about 1 month ago
Publisher: Oracle
Visit Github
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
61 debugging symbols found

Security

Vulnerabilities
2 severe vulnerabilities exploited
Hardening
6 baseline mitigations missing

Threats

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

Popularity

4.35M
Total Installs
1
Contributor
4
Declared Dependencies
3
Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.

Prevalence in Visual Studio Code community

71 packages
found in
Top 100
568 packages
found in
Top 1k
3198 packages
found in
Top 10k
16595 packages
in community

Next steps

We strongly advise updating 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

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

Prevalence in Visual Studio Code community

64 packages
found in
Top 100
445 packages
found in
Top 1k
2064 packages
found in
Top 10k
9214 packages
in community

Next steps

Perform impact analysis for the reported CVEs.
We strongly advise updating 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

Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Imported function addresses are pointers to the symbols that implement the application-required functionality. If those pointers are changed by malicious code, execution paths can be redirected to unintended locations. Most modern programming language toolchains protect those memory regions appropriately. These issues are commonly reported for outdated linkers and non-compliant executable packing solutions.

Prevalence in Visual Studio Code community

20 packages
found in
Top 100
156 packages
found in
Top 1k
474 packages
found in
Top 10k
1793 packages
in community

Next steps

Review the programming language linker options, and consider a build toolchain update.

Problem

Sensitive executable memory regions should be kept as read-only to protect the integrity of trusted execution code flow paths. Thread local storage (TLS) callbacks are pointers to code initialization and resource release functions. If those pointers are changed by malicious code, execution paths can be redirected to unintended locations. Most modern programming language toolchains protect those memory regions appropriately. These issues are commonly reported for outdated linkers and non-compliant executable packing solutions.

Prevalence in Visual Studio Code community

13 packages
found in
Top 100
101 packages
found in
Top 1k
347 packages
found in
Top 10k
1272 packages
in community

Next steps

Review the programming language linker options, and consider a build toolchain update.

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 Visual Studio Code community

72 packages
found in
Top 100
583 packages
found in
Top 1k
3344 packages
found in
Top 10k
17282 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.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
4 packages
found in
Top 100
14 packages
found in
Top 1k
40 packages
found in
Top 10k
149 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
48 packages
found in
Top 100
323 packages
found in
Top 1k
1111 packages
found in
Top 10k
4964 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
65 packages
found in
Top 100
535 packages
found in
Top 1k
2853 packages
found in
Top 10k
14133 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
28 packages
found in
Top 100
169 packages
found in
Top 1k
418 packages
found in
Top 10k
1486 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
23 packages
found in
Top 100
139 packages
found in
Top 1k
333 packages
found in
Top 10k
1311 packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(6 Active Vulnerabilities)
1 (1 Fixable)
CVE-2025-48924m
2 (2 Fixable)
CVE-2025-4949c
CVE-2022-4065h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for Java

What is Java?

Java Platform Extension for Visual Studio Code. For more information about this package, visit its homepage.

Is Java malicious or is it safe to use?

The VS Code package Java 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 Java popular?

The VS Code package Java ranks among the top 1000 projects in this community. It has 4M 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 Java once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Java behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Java 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.