CVE-2016-7043: Password in config file in KIE server

Summary

24/05/2022
Yes i
Critical
9.8

CVE-2016-7043: Password in config file in KIE server. Affects org.kie.server:kie-server-common versions < 7.21.0.Final. Fixed in 7.21.0.Final. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The KIE server and Business Central are software components used in the development and execution of business processes and rules. They provide a platform for deploying and managing applications that automate business processes. The KIE server is responsible for executing these applications, while Business Central serves as a web-based interface for designing and managing them. Both components are widely used in enterprise environments.

Vulnerability Detail

The KIE server and Business Central versions prior to 7.21.0.Final store the username and password as plaintext Java properties in a configuration file. This means that any application deployed on the same server can access these properties, potentially granting unauthorized access to sensitive services. An attacker with access to the configuration file can extract the credentials and use them to gain unauthorized access to the KIE server and Business Central, compromising the security and integrity of the system.

How To Fix

Minimum fixed version

7.21.0.Final

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 mentioned for this vulnerability. However, as a general best practice, it is recommended to regularly review and update the configuration files of the KIE server and Business Central to ensure that sensitive information, such as usernames and passwords, are not stored in plaintext. Additionally, access to these configuration files should be restricted to authorized personnel only.

Conclusion

The vulnerability (CVE-2016-7043) in the KIE server and Business Central versions prior to 7.21.0.Final allows unauthorized access to sensitive services due to the storage of plaintext credentials in a configuration file. To mitigate this risk, it is crucial to upgrade to the fixed version and properly secure the configuration files. Regularly reviewing and updating the configuration files is also recommended. For further assistance, contact DevNack.com.

See every vulnerability recorded for org.kie.server:kie-server-common →

Share this vulnerability

FAQ

This vulnerability allows unauthorized access to the KIE server and Business Central, potentially leading to unauthorized modification of business processes, data leakage, or disruption of critical services.

You can use the Vulert 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 of your application.

There are no known public exploits for this vulnerability at the time of this report. However, it is important to apply the recommended fix as soon as possible to mitigate the risk of potential exploits.

Securing the configuration file can help reduce the risk of unauthorized access to the credentials. However, it is still recommended to upgrade to the fixed version of the KIE server and Business Central to ensure a more robust and secure solution.

For further support on vulnerability remediation and assistance in upgrading to the fixed version, you can contact info@devnack.com. They can provide guidance and help ensure the security of your KIE server and Business Central installations.

How To Fix

Minimum fixed version

7.21.0.Final

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