CVE-2018-5399: Software Security Vulnerability Vulnerability
CRITICALCVE-2018-5399 is a CRITICAL (CVSS 9.8) security vulnerability vulnerability (CWE-798: Use of Hard-coded Credentials) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product contains hard-coded credentials, such as a password or cryptographic key.. Remediation is available in the latest vendor maintenance releases.
CVE-2018-5399 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2018-5399
To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2018-5399, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree
Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-798: Use of Hard-coded Credentials, where the product contains hard-coded credentials, such as a password or cryptographic key. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
References
Frequently Asked Questions
What is CVE-2018-5399?
Which Software versions are affected?
What version fixes CVE-2018-5399?
What is the CVSS score of CVE-2018-5399?
What CWE is associated with CVE-2018-5399?
How can I check Maven dependencies for CVE-2018-5399?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qxxm-7g2q-pwxw",
"modified" : "2022-05-13T01:32:11Z",
"published" : "2022-05-13T01:32:11Z",
"aliases" : [ "CVE-2018-5399" ],
"details" : "The Auto-Maskin DCU 210E firmware contains an undocumented Dropbear SSH server, v2015.55, configured to listen on Port 22 while the DCU is running. The Dropbear server is configured with a hard-coded user name and password combination of root / amroot. The server is configured to use password only authentication not cryptographic keys, however the firmware image contains an RSA host-key for the server. An attacker can exploit this vulnerability to gain root access to the Angstrom Linux operating system and modify any binaries or configuration files in the firmware. Affected releases are Auto-Maskin DCU-210E RP-210E: Versions prior to 3.7 on ARMv7.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2018-5399"
}, {
"type" : "WEB",
"url" : "https://www.kb.cert.org/vuls/id/176301"
}, {
"type" : "WEB",
"url" : "https://www.us-cert.gov/ics/advisories/icsa-20-051-04"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-798" ],
"severity" : "CRITICAL",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2018-10-08T15:29:00Z"
}
}