CVE-2020-17534: Improper synchronization in Apache Netbeans HTML/Java API

org.netbeans.html:pom Updated 02 Oct 2025

Summary

09/02/2022
Yes i
High
7.0

CVE-2020-17534: Improper synchronization in Apache Netbeans HTML/Java API. Affects org.netbeans.html:pom versions < 1.7.1. Fixed in 1.7.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Apache Netbeans HTML/Java API is a library that provides developers with the ability to create HTML/Java applications. It is commonly used in Java projects to build web-based user interfaces. The HTML/Java API version 1.7 is affected by a vulnerability that involves improper synchronization in the webkit subproject. This vulnerability allows for a race condition between the deletion of a temporary file and the creation of a temporary directory.

Vulnerability Detail

The race condition in the HTML/Java API version 1.7 can lead to local privilege escalation. An attacker could exploit this vulnerability to gain elevated privileges on the system. The issue arises due to the lack of atomic creation of the temporary directory, which can be manipulated by an attacker to execute arbitrary code or access sensitive information. The vulnerability has a CVSS score of 7.0, indicating a high severity level.

How To Fix

Minimum fixed version

1.7.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. It is crucial to update to the fixed version of the HTML/Java API to address the issue effectively.

Conclusion

The Apache Netbeans HTML/Java API version 1.7 is affected by a race condition vulnerability that can lead to local privilege escalation. To mitigate this risk, it is crucial to update to version 1.7.1 or later, which addresses the issue by ensuring the atomic creation of the temporary directory. It is recommended to use Vulert's playground (https://vulert.com/scanner) to check if your application is affected and to seek further support from DevNack.com for vulnerability remediation.

See every vulnerability recorded for org.netbeans.html:pom →

Share this vulnerability

FAQ

This vulnerability can lead to local privilege escalation, allowing an attacker to gain elevated privileges on the system.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using just the pom.xml file.

There are no known exploits for this vulnerability at the moment. However, it is essential to update to the fixed version to prevent potential attacks.

No, this vulnerability requires local access to the system to exploit it. However, it is still crucial to address the issue to prevent potential privilege escalation attacks.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide assistance and guidance in addressing this vulnerability.

How To Fix

Minimum fixed version

1.7.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback