CWE-798
Allowed-with-ReviewUse of Hard-coded Credentials
Abstraction: Base · Status: Draft
The product contains hard-coded credentials, such as a password or cryptographic key.
2185 vulnerabilities reference this CWE, most recent first.
GHSA-7JG2-G39F-M6PF
Vulnerability from github – Published: 2022-05-14 03:19 – Updated: 2022-05-14 03:19Directus 6.4.9 has a hardcoded admin password for the Admin account because of an INSERT statement in api/schema.sql.
{
"affected": [],
"aliases": [
"CVE-2018-10723"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-05-05T22:29:00Z",
"severity": "CRITICAL"
},
"details": "Directus 6.4.9 has a hardcoded admin password for the Admin account because of an INSERT statement in api/schema.sql.",
"id": "GHSA-7jg2-g39f-m6pf",
"modified": "2022-05-14T03:19:31Z",
"published": "2022-05-14T03:19:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-10723"
},
{
"type": "WEB",
"url": "https://gist.github.com/llandeilocymro/2438a0b5aba8b387c86d7e3181ecbe76"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7JHJ-M58M-CG57
Vulnerability from github – Published: 2024-04-19 06:30 – Updated: 2025-02-04 18:30Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appliance's root password. The vulnerability could allow an unauthenticated attacker full access to the Brocade SANnav appliance.
{
"affected": [],
"aliases": [
"CVE-2024-29966"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-04-19T05:15:49Z",
"severity": "HIGH"
},
"details": "Brocade SANnav OVA before v2.3.1 and v2.3.0a contain hard-coded credentials in the documentation that appear as the appliance\u0027s root password. The vulnerability could allow an unauthenticated attacker full access to the Brocade SANnav appliance.",
"id": "GHSA-7jhj-m58m-cg57",
"modified": "2025-02-04T18:30:44Z",
"published": "2024-04-19T06:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-29966"
},
{
"type": "WEB",
"url": "https://support.broadcom.com/external/content/SecurityAdvisories/0/23255"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-7JM2-V68F-WW8P
Vulnerability from github – Published: 2022-03-22 00:00 – Updated: 2022-03-29 00:01Multiple versions of GARO Wallbox GLB/GTB/GTC are affected by hard coded credentials. A hardcoded credential exist in /etc/tomcat8/tomcat-user.xml, which allows attackers to gain authorized access and control the tomcat completely on port 8000 in the tomcat manger page.
{
"affected": [],
"aliases": [
"CVE-2021-45877"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-03-21T11:15:00Z",
"severity": "CRITICAL"
},
"details": "Multiple versions of GARO Wallbox GLB/GTB/GTC are affected by hard coded credentials. A hardcoded credential exist in /etc/tomcat8/tomcat-user.xml, which allows attackers to gain authorized access and control the tomcat completely on port 8000 in the tomcat manger page.",
"id": "GHSA-7jm2-v68f-ww8p",
"modified": "2022-03-29T00:01:28Z",
"published": "2022-03-22T00:00:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-45877"
},
{
"type": "WEB",
"url": "https://github.com/delikely/advisory/tree/main/GARO"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7JMH-HG7G-G34F
Vulnerability from github – Published: 2022-05-14 03:19 – Updated: 2022-05-14 03:19The presence of a hardcoded account in Fortinet FortiWLC 8.3.3 allows attackers to gain unauthorized read/write access via a remote shell.
{
"affected": [],
"aliases": [
"CVE-2017-17540"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-05-08T04:29:00Z",
"severity": "CRITICAL"
},
"details": "The presence of a hardcoded account in Fortinet FortiWLC 8.3.3 allows attackers to gain unauthorized read/write access via a remote shell.",
"id": "GHSA-7jmh-hg7g-g34f",
"modified": "2022-05-14T03:19:30Z",
"published": "2022-05-14T03:19:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-17540"
},
{
"type": "WEB",
"url": "https://fortiguard.com/advisory/FG-IR-17-274"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/104119"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7JP2-R62F-6M58
Vulnerability from github – Published: 2022-05-24 19:02 – Updated: 2022-05-24 19:02SITEL CAP/PRX firmware version 5.2.01 makes use of a hardcoded password. An attacker with access to the device could modify these credentials, leaving the administrators of the device without access.
{
"affected": [],
"aliases": [
"CVE-2021-32454"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-05-17T18:15:00Z",
"severity": "HIGH"
},
"details": "SITEL CAP/PRX firmware version 5.2.01 makes use of a hardcoded password. An attacker with access to the device could modify these credentials, leaving the administrators of the device without access.",
"id": "GHSA-7jp2-r62f-6m58",
"modified": "2022-05-24T19:02:35Z",
"published": "2022-05-24T19:02:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-32454"
},
{
"type": "WEB",
"url": "https://www.incibe-cert.es/en/early-warning/ics-advisories/sitel-capprx-hardcoded-credentials"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-7JRR-6MXP-R8V9
Vulnerability from github – Published: 2022-06-03 00:00 – Updated: 2022-06-14 00:00A CWE-798: Use of Hard-coded Credentials vulnerability exists that could allow arbitrary code to be executed when root level access is obtained. Affected Products: Wiser Smart, EER21000 & EER21001 (V4.5 and prior)
{
"affected": [],
"aliases": [
"CVE-2022-30234"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-06-02T23:15:00Z",
"severity": "CRITICAL"
},
"details": "A CWE-798: Use of Hard-coded Credentials vulnerability exists that could allow arbitrary code to be executed when root level access is obtained. Affected Products: Wiser Smart, EER21000 \u0026 EER21001 (V4.5 and prior)",
"id": "GHSA-7jrr-6mxp-r8v9",
"modified": "2022-06-14T00:00:30Z",
"published": "2022-06-03T00:00:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-30234"
},
{
"type": "WEB",
"url": "https://www.se.com/ww/en/download/document/SEVD-2022-130-03"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7M5H-J2PG-2JR2
Vulnerability from github – Published: 2022-05-24 17:11 – Updated: 2026-06-03 15:30Rockwell Automation MicroLogix 1400 Controllers Series B v21.001 and prior, Series A, all versions, MicroLogix 1100 Controller, all versions, RSLogix 500 Software v12.001 and prior, The cryptographic key utilized to help protect the account password is hard coded into the RSLogix 500 binary file. An attacker could identify cryptographic keys and use it for further cryptographic attacks that could ultimately lead to a remote attacker gaining unauthorized access to the controller.
{
"affected": [],
"aliases": [
"CVE-2020-6990"
],
"database_specific": {
"cwe_ids": [
"CWE-321",
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-03-16T16:15:00Z",
"severity": "HIGH"
},
"details": "Rockwell Automation MicroLogix 1400 Controllers Series B v21.001 and prior, Series A, all versions, MicroLogix 1100 Controller, all versions, RSLogix 500 Software v12.001 and prior, The cryptographic key utilized to help protect the account password is hard coded into the RSLogix 500 binary file. An attacker could identify cryptographic keys and use it for further cryptographic attacks that could ultimately lead to a remote attacker gaining unauthorized access to the controller.",
"id": "GHSA-7m5h-j2pg-2jr2",
"modified": "2026-06-03T15:30:33Z",
"published": "2022-05-24T17:11:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-6990"
},
{
"type": "WEB",
"url": "https://www.us-cert.gov/ics/advisories/icsa-20-070-06"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7M72-36WH-C4FR
Vulnerability from github – Published: 2022-05-24 16:46 – Updated: 2024-04-04 00:45Computrols CBAS 18.0.0 has Default Credentials.
{
"affected": [],
"aliases": [
"CVE-2019-10850"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-05-23T20:29:00Z",
"severity": "CRITICAL"
},
"details": "Computrols CBAS 18.0.0 has Default Credentials.",
"id": "GHSA-7m72-36wh-c4fr",
"modified": "2024-04-04T00:45:39Z",
"published": "2022-05-24T16:46:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-10850"
},
{
"type": "WEB",
"url": "https://applied-risk.com/index.php/download_file/view/196/165"
},
{
"type": "WEB",
"url": "https://applied-risk.com/labs/advisories"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-7M73-7MCC-V47J
Vulnerability from github – Published: 2022-05-13 01:50 – Updated: 2022-05-13 01:50The EPSON iPrint application 6.6.3 for Android contains hard-coded API and Secret keys for the Dropbox, Box, Evernote and OneDrive services.
{
"affected": [],
"aliases": [
"CVE-2018-14901"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-08-30T17:29:00Z",
"severity": "HIGH"
},
"details": "The EPSON iPrint application 6.6.3 for Android contains hard-coded API and Secret keys for the Dropbox, Box, Evernote and OneDrive services.",
"id": "GHSA-7m73-7mcc-v47j",
"modified": "2022-05-13T01:50:03Z",
"published": "2022-05-13T01:50:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-14901"
},
{
"type": "WEB",
"url": "https://www.vdalabs.com/2018/08/26/epson-printer-vulnerabilities"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-7MRW-X9JW-7W68
Vulnerability from github – Published: 2022-05-24 22:28 – Updated: 2022-05-24 22:28In SapphireIMS 5.0, it is possible to use the hardcoded credential in clients (username: sapphire, password: ims) and gain access to the portal. Once the access is available, the attacker can inject malicious OS commands on “ping”, “traceroute” and “snmp” functions and execute code on the server.
{
"affected": [],
"aliases": [
"CVE-2020-25565"
],
"database_specific": {
"cwe_ids": [
"CWE-798"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-08-11T21:15:00Z",
"severity": "CRITICAL"
},
"details": "In SapphireIMS 5.0, it is possible to use the hardcoded credential in clients (username: sapphire, password: ims) and gain access to the portal. Once the access is available, the attacker can inject malicious OS commands on \u201cping\u201d, \u201ctraceroute\u201d and \u201csnmp\u201d functions and execute code on the server.",
"id": "GHSA-7mrw-x9jw-7w68",
"modified": "2022-05-24T22:28:22Z",
"published": "2022-05-24T22:28:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-25565"
},
{
"type": "WEB",
"url": "https://vuln.shellcoder.party/2020/09/19/cve-2020-25565-sapphireims-unprivileged-user-remote-command-execution-on-server"
},
{
"type": "WEB",
"url": "https://vuln.shellcoder.party/tags/sapphireims"
}
],
"schema_version": "1.4.0",
"severity": []
}
Mitigation
- For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7].
- In Windows environments, the Encrypted File System (EFS) may provide some protection.
Mitigation
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Mitigation
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
Mitigation
- For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash.
- Use randomly assigned salts for each separate hash that is generated. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
Mitigation
- For front-end to back-end connections: Three solutions are possible, although none are complete.
- The first suggestion involves the use of generated passwords or keys that are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals.
- Next, the passwords or keys should be limited at the back end to only performing actions valid for the front end, as opposed to having full access.
- Finally, the messages sent should be tagged and checksummed with time sensitive values so as to prevent replay-style attacks.
CAPEC-191: Read Sensitive Constants Within an Executable
An adversary engages in activities to discover any sensitive constants present within the compiled code of an executable. These constants may include literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis.
CAPEC-70: Try Common or Default Usernames and Passwords
An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.