Weakness (CWE)
CWE-522: Insufficiently Protected Credentials
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
How to prevent it (3 mitigations)
-
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
-
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
-
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
Source: MITRE CWE-522
1,021 results · Feed
-
High 7.5
Incorrect implementation of lockout feature in Keycloak
A flaw was found in keycloak where a brute force attack is possible even when the permanent lockout feature is enabled. This is due to a wrong error message displayed when wrong credentials are entered. The highest threat from this vulnerability is to confide…
-
Medium 5.5
Insufficiently protected credentials in the Intel(R) Team Blue mobile application in all versions may allow an authenti…
-
High 7.5
Insufficiently protected credentials in the Intel(R) Datacenter Group Event iOS application, all versions, may allow an…
-
High 7.8
Insufficiently protected credentials in the installation binaries for Intel(R) SEAPI in all versions may allow an authe…
-
Critical 9.8
Insufficiently protected credentials for Intel(R) AMT and Intel(R) Standard Manageability may allow an unauthenticated …
-
Medium 5.5
Insufficiently protected credentials for Intel(R) AMT and Intel(R) Standard Manageability may allow a privileged user t…
-
Unscored —
The AirVelocity 1500 prints SNMP credentials on its physically accessible serial port during boot. This was fixed in Ai…
-
Unscored —
A flaw was found where the Plaintext Candlepin password is disclosed while updating Red Hat Satellite through the satel…
-
Low 3.9
HCL Commerce could allow a local attacker to obtain sensitive personal information (CVE-2021-27785)
HCL Commerce's Remote Store server could allow a local attacker to obtain sensitive personal information. The vulnerability requires the victim to first perform a particular operation on the website.
-
High 7.5
Ovarro TBox Insufficiently Protected Credentials
An attacker can decrypt the Ovarro TBox login password by communication capture and brute force attacks.
-
Unscored —
Anchore Enterprise anchorectl version 0.1.4 improperly stored credentials when generating a Software Bill of Materials.…
-
Medium 5.0
HCL BigFix Web Reports authorized users may see sensitive information in clear text
BigFix Web Reports authorized users may see SMTP credentials in clear text.
-
High 8.0
Protecting AWS credentials stored in plaintext on My Cloud Home
Implemented protections on AWS credentials that were not properly protected.
-
Critical 9.8
rpc.py vulnerable to Deserialization of Untrusted Data
rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTTP header is sent. In other words, although JSON (not Pickle) is the default data format, an unauthenticated client can cause the data to be processed…
-
High 7.7
PingID Windows Login prior to 2.8 does not properly set permissions on the Windows Registry entries used to store sensitive API keys under some circumstances
PingID Windows Login prior to 2.8 does not properly set permissions on the Windows Registry entries used to store sensitive API keys under some circumstances.
-
Low 3.3
Passwords stored in plain text by Jenkins hpe-network-virtualization plugin
Jenkins HPE Network Virtualization Plugin 1.0 stores passwords unencrypted in its global configuration file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.
-
Low 3.3
Password stored in plain text by Jenkins RQM Plugin
Jenkins RQM Plugin 2.8 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
-
Low 3.3
Token stored in plain text by Jenkins Cisco Spark Plugin
Jenkins Cisco Spark Plugin 1.1.1 and earlier stores bearer tokens unencrypted in its global configuration file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.
-
Low 3.3
Plaintext Storage of a Password in Jenkins Elasticsearch Query Plugin
Jenkins Elasticsearch Query Plugin 1.2 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
-
Low 3.3
Plaintext Storage of a Password in Jenkins Jigomerge Plugin
Jenkins Jigomerge Plugin 0.9 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller file system.
-
Low 3.3
Plaintext Storage of a Password in Jenkins Skype notifier Plugin
Jenkins Skype notifier Plugin 1.1.0 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
-
Medium 4.3
Jenkins OpsGenie Plugin Plaintext Storage of a Password vulnerability
Jenkins OpsGenie Plugin 1.9 and earlier stores API keys unencrypted in its global configuration file and in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission (config.xml), or access to the Jenkins c…
-
Low 3.3
Plaintext Storage of a Password in Jenkins RocketChat Notifier Plugin
Jenkins RocketChat Notifier Plugin 1.5.2 and earlier stores the login password and webhook token unencrypted in its global configuration file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.
-
Low 3.3
Plaintext Storage of a Password in Jenkins Build Notifications Plugin
Jenkins Build Notifications Plugin 1.5.0 and earlier stores tokens unencrypted in its global configuration files on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.
-
Low 3.3
Plaintext Storage of a Password in Jenkins Deployment Dashboard Plugin
Jenkins Deployment Dashboard Plugin 1.0.10 and earlier stores a password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
-
Medium 4.3
Jenkins Deployment Dashboard Plugin has Insufficiently Protected Credentials
A missing permission check in Jenkins Deployment Dashboard Plugin 1.0.10 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
-
Medium 6.5
Secheron SEPCOS Control and Protection Relay
The default password for the web application’s root user (the vendor’s private account) was weak and the MD5 hash was used to crack the password using a widely available open-source tool.
-
Low 3.3
Squash TM Publisher (Squash4Jenkins) Plugin stores passwords stored in plain text
Jenkins Squash TM Publisher (Squash4Jenkins) Plugin 1.0.0 and earlier stores passwords unencrypted in its global configuration file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.
-
Medium 4.3
Plaintext Storage of a Password in Jenkins Convertigo Mobile Platform Plugin
Jenkins Convertigo Mobile Platform Plugin 1.1 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller file system.
-
High 7.5
Insufficiently Protected Credentials in PowerJob
An issue was discovered in PowerJob through 3.2.2, allows attackers to change arbitrary user passwords via the id parameter to /appinfo/save.
-
High 7.5
Plaintext Storage of Keys and Passwords in Rundeck and PagerDuty Process Automation
Rundeck is an open source automation service with a web console, command line tools and a WebAPI. The Key Storage converter plugin mechanism was not enabled correctly in Rundeck 4.2.0 and 4.2.1, resulting in use of the encryption layer for Key Storage possibl…
-
Medium 5.9
Authorization header leak in rubygem Mechanize
The Mechanize library is used for automating interaction with websites. Mechanize automatically stores and sends cookies, follows redirects, and can follow links and submit forms. In versions prior to 2.8.5 the Authorization header is leaked after a redirect …
-
Unscored —
A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header…
-
Medium 5.7
An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that c…
-
Medium 5.3
Insufficiently Protected Credentials in Jenkins Pipeline SCM API for Blue Ocean Plugin
Jenkins Pipeline SCM API for Blue Ocean Plugin 1.25.3 and earlier allows attackers with Job/Configure permission to access credentials with attacker-specified IDs stored in the private per-user credentials stores of any attacker-specified user in Jenkins.
-
Critical 9.8
Account Takeover in neorazorx/facturascripts
Account Takeover in GitHub repository neorazorx/facturascripts prior to 2022.07.
-
High 7.3
Exposure of repository credentials to external third-party sources
A Incorrect Authorization vulnerability in SUSE Rancher allows administrators of third-party repositories to gather credentials that are sent to their servers. This issue affects: SUSE Rancher Rancher versions prior to 2.5.12; Rancher versions prior to 2.6.3.
-
High 8.2
Dell EMC Repository Manager version 3.4.0 contains a plain-text password storage vulnerability. A local attacker could …
-
Medium 4.6
ICSA-22-104-03 Red Lion DA50N
A malicious actor having access to the exported configuration file may obtain the stored credentials and thereby gain access to the protected resource. If the same passwords were used for other resources, further such assets may be compromised.
-
Unscored —
A flaw was found in Ansible Galaxy Collections. When collections are built manually, any files in the repository direct…