Skip to content
OpenAdvisories

Weakness (CWE)

CWE-326: Inadequate Encryption Strength

Class Draft

The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.

How to prevent it (1 mitigation)
  1. Architecture and Design

    Use an encryption scheme that is currently considered to be strong by experts in the field.

Source: MITRE CWE-326

246 results · Feed

  • Medium —

    Jenkins Subversion Plugin Stores Credentials with Base64 Encoding

    The Subversion plugin before 1.54 for Jenkins stores credentials using base64 encoding, which allows local users to obtain passwords and SSH private keys by reading a subversion.credentials file.

  • Medium —
    CVE-2012-5575 Public exploit

    Inadequate Encryption Strength in Apache CXF

    Apache CXF 2.5.x before 2.5.10, 2.6.x before CXF 2.6.7, and 2.7.x before CXF 2.7.4 does not verify that a specified cryptographic algorithm is allowed by the WS-SecurityPolicy AlgorithmSuite definition before decrypting, which allows remote attackers to force…

  • High 7.5

    Python Keyring does not securely initialize encryption cipher

    Python Keyring 0.9.1 does not securely initialize the cipher when encrypting passwords for CryptedFileKeyring files, which makes it easier for local users to obtain passwords via a brute-force attack.

  • Medium 5.3

    Beaker Sensitive Information Disclosure vulnerability

    Beaker before 1.6.4, when using PyCrypto to encrypt sessions, uses AES in ECB cipher mode, which might allow remote attackers to obtain portions of sensitive session data via unspecified vectors.

  • High 7.8
    CVE-2001-1546 Public exploit

    Pathways Homecare 6.5 uses weak encryption for user names and passwords, which allows local users to gain privileges by…

  • Medium 5.5

    Sharp Zaurus PDA SL-5000D and SL-5500 uses a salt of "A0" to encrypt the screen-locking password as stored in the Secur…