Skip to content
OpenAdvisories

Weakness (CWE)

CWE-311: Missing Encryption of Sensitive Data

Class Draft Mapping discouraged

The product does not encrypt sensitive or critical information before storage or transmission.

How to prevent it (6 mitigations)
  1. Requirements

    Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.

  2. Architecture and Design

    Ensure that encryption is properly integrated into the system design, including but not necessarily limited to:

    - Encryption that is needed to store or transmit private data of the users of the system

    - Encryption that is needed to protect the system itself from unauthorized disclosure or tampering

    Identify the separate needs and contexts for encryption:

    - One-way (i.e., only the user or recipient needs to have the key). This can be achieved using public key cryptography, or other techniques in which the encrypting party (i.e., the product) does not need to have access to a private key.

    - Two-way (i.e., the encryption can be automatically performed on behalf of a user, but the key must be available so that the plaintext can be automatically recoverable by that user). This requires storage of the private key in a format that is recoverable only by the user (or perhaps by the operating system) in a way that cannot be recovered by others.

    Using threat modeling or other techniques, assume that data can be compromised through a separate vulnerability or weakness, and determine where encryption will be most effective. Ensure that data that should be private is not being inadvertently exposed using weaknesses such as insecure permissions (CWE-732). [REF-7]

  3. Architecture and Design

    When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations. As with all cryptographic mechanisms, the source code should be available for analysis.

    For example, US government systems require FIPS 140-2 certification.

    Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. Reverse engineering techniques are mature. If the algorithm can be compromised if attackers find out how it works, then it is especially weak.

    Periodically ensure that the cryptography has not become obsolete. Some older algorithms, once thought to require a billion years of computing time, can now be broken in days or hours. This includes MD4, MD5, SHA1, DES, and other algorithms that were once regarded as strong. [REF-267]

  4. Architecture and Design

    Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

    Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

  5. Implementation, Architecture and Design

    When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.

  6. Implementation

    Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.

Source: MITRE CWE-311

383 results · Feed

  • Medium 5.9

    Jenkins Active Directory Plugin vulnerable to Active Directory credential disclosure

    Jenkins Active Directory Plugin 2.30 and earlier ignores the "Require TLS" and "StartTls" options and always performs the connection test to Active directory unencrypted, allowing attackers able to capture network traffic between the Jenkins controller and Ac…

  • Low 3.7

    IBM CICS TX information disclosure

    IBM TXSeries for Multiplatforms 8.1, 8.2, 9.1, CICS TX Standard, 11.1, CICS TX Advanced 10.1, and 11.1 could transmit sensitive information in query parameters that could be intercepted using man in the middle techniques. IBM X-Force ID: 257105.

  • Medium 6.3

    Dell CloudIQ Collector version 1.10.2 contains a missing encryption of sensitive data vulnerability. An attacker with l…

  • Medium 4.3

    Jenkins Ansible Plugin stores and displays secrets in plain text

    Jenkins Ansible Plugin 204.v8191fd551eb_f and earlier stores extra variables unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.

  • Medium 4.9

    An issue was discovered in TigerGraph Enterprise Free Edition 3.x. There is unsecured read access to an SSH private key…

  • Medium 4.3

    Jenkins Report Portal Plugin allows users with Item/Extended Read permission to view tokens on Jenkins controller

    Jenkins Report Portal Plugin 0.5 and earlier stores ReportPortal access tokens unencrypted in job config.xml files on the Jenkins controller as part of its configuration where they can be viewed by users with Item/Extended Read permission or access to the Jen…

  • Medium 6.8

    moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted

    Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby is commonly r…

  • Medium 6.5

    A cleartext transmission vulnerability exists in the Remote Management functionality of Netgear Orbi Router RBR750 4.6.…

  • Medium 5.0

    Boundary Workers Store Rotated Credentials in Plaintext Even When a Key Management Service Configured

    HashiCorp Boundary from 0.10.0 through 0.11.2 contain an issue where when using a PKI-based worker with a Key Management Service (KMS) defined in the configuration file, new credentials created after an automatic rotation may not have been encrypted via the i…

  • Medium 5.3

    In Last Yard 22.09.8-1, the cookie can be stolen via via unencrypted traffic.

  • Low 3.7

    Macaron csrf csrf.go missing secure attribute

    A vulnerability was found in Macaron csrf and classified as problematic. Affected by this issue is some unknown functionality of the file csrf.go. The manipulation of the argument Generate leads to sensitive cookie without secure attribute. The attack may be …

  • High 7.5

    Weak encryption and denial of service in github.com/flynn/noise

    The Noise protocol implementation suffers from weakened cryptographic security after encrypting 2^64 messages, and a potential denial of service attack. After 2^64 (~18.4 quintillion) messages are encrypted with the Encrypt function, the nonce counter will wr…

  • Medium 4.3

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in usememos/memos

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository usememos/memos prior to 0.9.0.

  • High 7.7

    HCL BigFix Server Automation (SA) is affected by a security vulnerability around Notification Service

    BigFix deployments that have installed the Notification Service on Windows are susceptible to disclosing SMTP BigFix operator's sensitive data in clear text. Operators who use Notification Service related content from BES Support are at risk of leaving their …

  • Medium 6.3

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in thorsten/phpmyfaq

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository thorsten/phpmyfaq prior to 3.1.9.

  • Medium 6.5

    Dashlane password and Keepass Server password in My Account Settings  are not encrypted in the database in Devolutions …

  • Medium 4.8

    The physical IoT device of the AliveCor's KardiaMobile, a smartphone-based personal electrocardiogram (EKG) has no encr…

  • Medium 6.8

    Missing AES encryption in Corsair K63 Wireless 3.1.3 allows physically proximate attackers to inject and sniff keystrok…

  • Medium 4.9

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in ikus060/rdiffweb

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository ikus060/rdiffweb prior to 2.4.6.

  • Unscored —

    Under certain conditions SAP BusinessObjects Business Intelligence Platform Central Management Console (CMC) - version …

  • High 7.5

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in ikus060/rdiffweb

    Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository ikus060/rdiffweb prior to 2.4.2.

  • Medium 4.2

    Unencrypted internal storage of security credentials

    The Baxter Spectrum Wireless Battery Module (WBM) stores network credentials and PHI (only applicable to Spectrum IQ pumps using auto programming) in unencrypted form. An attacker with physical access to a device that hasn't had all data and settings erased m…

  • Medium 6.7

    Portal for ArcGIS system properties are not properly encrypted (10.8.1 only)

    In Esri Portal for ArcGIS versions 10.8.1, a system property is not properly encrypted. This may lead to a local user reading sensitive information from a properties file.

  • Medium 4.7

    Dell BSAFE Crypto-C Micro Edition, versions before 4.1.5, and Dell BSAFE Micro Edition Suite, versions before 4.6, cont…

  • Medium 5.3

    Insecure cookies in Openshift Origin

    In Openshift Origin 3 the cookies being set in console have no 'secure', 'HttpOnly' attributes.

  • High 7.5
    CVE-2022-2097 Public exploit

    AES OCB fails to encrypt some bytes

    AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the…

  • Medium 5.5

    Missing Encryption of Sensitive Data in ldap-account-manager

    LDAP Account Manager (LAM) is a webfrontend for managing entries (e.g. users, groups, DHCP settings) stored in an LDAP directory. In versions prior to 8.0 the session files include the LDAP user name and password in clear text if the PHP OpenSSL extension is …

  • High 8.2

    A CWE-311: Missing Encryption of Sensitive Data vulnerability exists that could allow authentication credentials to be …

  • Medium 6.8

    HCL BigFix Mobile / Modern Client Management is vulnerable to sensitive information exposure

    User generated PPKG file for Bulk Enroll may have unencrypted sensitive information exposed.

  • Critical 9.1

    A Security Misconfiguration vulnerability affects HCL VersionVault Express

    VersionVault Express exposes sensitive information that an attacker can use to impersonate the server or eavesdrop on communications with the server.

  • Medium 6.8

    Rancher: Weave CNI password is not set if RKE template is used with CNI value overridden

    A Cleartext Transmission of Sensitive Information vulnerability in SUSE Rancher, Rancher allows attackers on the network to read and change network data due to missing encryption of data transmitted via the network when a cluster is created from an RKE templa…

  • Low 3.3

    Client Secret stored in plain text by Jenkins GitLab Authentication Plugin

    Jenkins GitLab Authentication Plugin 1.13 and earlier stores the GitLab client secret unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

  • High 7.4

    An information disclosure vulnerability exists in the Web Server functionality of Sealevel Systems, Inc. SeaConnect 370…

  • Medium 5.3

    Agent-to-controller security bypass in Jenkins Conjur Secrets Plugin allows decrypting secrets

    Jenkins Conjur Secrets Plugin 1.0.9 and earlier implements functionality that allows attackers able to control agent processes to decrypt secrets stored in Jenkins obtained through another method.

  • Unscored —

    Z-Wave devices based on Silicon Labs 500 series chipsets using CRC-16 encapsulation, including but likely not limited t…

  • Unscored —

    Z-Wave devices based on Silicon Labs 100, 200, and 300 series chipsets do not support encryption, allowing an attacker …

  • Unscored —

    A vulnerability has been identified in Climatix POL909 (AWB module) (All versions < V11.42), Climatix POL909 (AWM modul…

  • Medium 5.7

    In Arista's EOS software affected releases, the shared secret profiles sensitive configuration might be leaked when displaying output over eAPI or other JSON outputs to authenticated users on the device.

    On systems running Arista EOS and CloudEOS with the affected release version, when using shared secret profiles the password configured for use by BiDirectional Forwarding Detection (BFD) will be leaked when displaying output over eAPI or other JSON outputs t…

  • Medium 5.3

    Junos OS: When using J-Web with HTTP an attacker may retrieve encryption keys via Person-in-the-Middle attacks.

    A Protection Mechanism Failure vulnerability in the J-Web HTTP service of Juniper Networks Junos OS allows a remote unauthenticated attacker to perform Person-in-the-Middle (PitM) attacks against the device. This issue affects: Juniper Networks Junos OS 12.3 …

  • High 7.3

    ECOA BAS controller - Missing Encryption of Sensitive Data

    ECOA BAS controller stores sensitive data (backup exports) in clear-text, thus the unauthenticated attacker can remotely query user password and obtain user’s privilege.