What is CVE-2022-39259?

CVE-2022-39259 is a medium-severity security vulnerability in io.github.skylot:jadx-plugins-api (maven), affecting versions <= 1.4.4. It is fixed in 1.4.5.

How severe is CVE-2022-39259?

CVE-2022-39259 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of io.github.skylot:jadx-plugins-api are affected by CVE-2022-39259?

io.github.skylot:jadx-plugins-api (maven) versions <= 1.4.4 is affected.

Is there a fix for CVE-2022-39259?

Yes. CVE-2022-39259 is fixed in 1.4.5. Upgrade to this version or later.

Is CVE-2022-39259 exploitable, and should I be worried?

Whether CVE-2022-39259 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-39259 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-39259 in io.github.skylot:jadx-plugins-api

Q: How severe is CVE-2022-39259?

CVE-2022-39259 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of io.github.skylot:jadx-plugins-api are affected by CVE-2022-39259?

io.github.skylot:jadx-plugins-api (maven) versions <= 1.4.4 is affected.

Q: Is there a fix for CVE-2022-39259?

Yes. CVE-2022-39259 is fixed in 1.4.5. Upgrade to this version or later.

Q: Is CVE-2022-39259 exploitable, and should I be worried?

Whether CVE-2022-39259 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-39259 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-39259?

Upgrade io.github.skylot:jadx-plugins-api to 1.4.5 or later.

Summary

Jadx-gui vulnerable to swing HTML Denial of Service (DoS) attack

References

https://www.oracle.com/java/technologies/javase/seccodeguide.html

Guideline 3-7 / INJECT-7: Disable HTML display in Swing components:

Many Swing pluggable look-and-feels interpret text in certain components starting with as HTML. If the text is from an untrusted source, an adversary may craft the HTML such that other components appear to be present or to perform inclusion attacks.

To disable the HTML render feature, set the "html.disable" client property of each component to Boolean.TRUE (no other Boolean true instance will do).

label.putClientProperty("html.disable", true);

Impact

Using jadx-gui to open a special zip file with entry containing HTML sequence like <html><frame> will cause interface to get stuck and throw exceptions like:

java.lang.RuntimeException: Can't build aframeset, BranchElement(frameset) 1,3
:no ROWS or COLS defined.
	at java.desktop/javax.swing.text.html.HTMLEditorKit$HTMLFactory.create(HTMLEditorKit.java:1387)
	at java.desktop/javax.swing.plaf.basic.BasicHTML$BasicHTMLViewFactory.create(BasicHTML.java:379)
	at java.desktop/javax.swing.text.CompositeView.loadChildren(CompositeView.java:112)

CVE-2022-39259 has a CVSS score of 5.5 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.5); upgrading removes the vulnerable code path.

Affected versions

io.github.skylot:jadx-plugins-api (<= 1.4.4)

Security releases

io.github.skylot:jadx-plugins-api → 1.4.5 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade io.github.skylot:jadx-plugins-api to 1.4.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-39259? CVE-2022-39259 is a medium-severity security vulnerability in io.github.skylot:jadx-plugins-api (maven), affecting versions <= 1.4.4. It is fixed in 1.4.5.
How severe is CVE-2022-39259? CVE-2022-39259 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of io.github.skylot:jadx-plugins-api are affected by CVE-2022-39259? io.github.skylot:jadx-plugins-api (maven) versions <= 1.4.4 is affected.
Is there a fix for CVE-2022-39259? Yes. CVE-2022-39259 is fixed in 1.4.5. Upgrade to this version or later.
Is CVE-2022-39259 exploitable, and should I be worried? Whether CVE-2022-39259 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-39259 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-39259? Upgrade io.github.skylot:jadx-plugins-api to 1.4.5 or later.