Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: 9 days ago

ExtendScript Debugger

Artifact:
latest
Top 10k
Enables debugging ExtendScript-based extensions in Adobe’s applications that support ExtendScript extensions.
License: Permissive (Apache-2.0)
Published: 5 months ago
Publisher: Adobe
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 severe vulnerabilities exploited
Hardening
2 misconfigured toolchains detected

Threats

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

Popularity

129.4k
Total Installs
1
Contributor
3
Declared Dependencies
0
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

67 packages
found in
Top 100
548 packages
found in
Top 1k
3078 packages
found in
Top 10k
17.39k 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 high severity.

Prevalence in Visual Studio Code community

68 packages
found in
Top 100
555 packages
found in
Top 1k
3086 packages
found in
Top 10k
17.47k 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

Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors, preventing them from reaching production. These checks minimize the number of security issues by enforcing strict memory access checks. They also prevent the use of hard-to-secure string and memory manipulation functions. To prove the binary has been compiled with these checks enabled, the compiler emits a special debug object. Removing the debug table eliminates this proof. Therefore, this check only applies to binaries that still have their debug tables.

Prevalence in Visual Studio Code community

43 packages
found in
Top 100
257 packages
found in
Top 1k
754 packages
found in
Top 10k
3.7k packages
in community

Next steps

You should keep the debug table to prove that the SDL process has been followed.
To enable these checks, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.

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 medium severity.

Prevalence in Visual Studio Code community

64 packages
found in
Top 100
530 packages
found in
Top 1k
2998 packages
found in
Top 10k
16.52k 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

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in Visual Studio Code community

53 packages
found in
Top 100
442 packages
found in
Top 1k
3405 packages
found in
Top 10k
57.88k packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
26 packages
found in
Top 100
136 packages
found in
Top 1k
330 packages
found in
Top 10k
1.5k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
31 packages
found in
Top 100
159 packages
found in
Top 1k
346 packages
found in
Top 10k
1.56k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
17 packages
found in
Top 100
74 packages
found in
Top 1k
247 packages
found in
Top 10k
1.08k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
94 packages
found in
Top 100
837 packages
found in
Top 1k
6746 packages
found in
Top 10k
87.76k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
52 packages
found in
Top 100
290 packages
found in
Top 1k
981 packages
found in
Top 10k
4.36k packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(4 Active Vulnerabilities)
2 (2 Fixable)
CVE-2023-34104h
CVE-2025-6965h
2 (2 Fixable)
CVE-2022-35737h
CVE-2023-26920m
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for ExtendScript Debugger

What is ExtendScript Debugger?

Enables debugging ExtendScript-based extensions in Adobe’s applications that support ExtendScript extensions.

Is ExtendScript Debugger malicious or is it safe to use?

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

The VS Code package ExtendScript Debugger ranks among the top 10000 projects in this community. It has 129K 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 ExtendScript Debugger once it is in my app?

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