Crypto-View

wultra/powerauth-crypto

Cryptographic posture

267 cryptographic locations: 57 quantum-vulnerable, 38 reduced-margin, 104 undetermined, 68 quantum-safe

19 establish keys, so traffic protected by them and recorded today becomes readable once the algorithm falls. 1 imported cryptographic library is listed separately. 206 files analysed.

Quantum-vulnerable 57 Reduced margin 38 Could not be determined 104 Quantum-safe 68
To address92
Key establishment19
Inventory only1
Total findings268
What was analysed
Branch develop
Commit 2a4c1d787efbf6785a897b5b1a4f5da1fa9c79c2 Bump org.sonatype.central:central-publishing-maven-plugin (#989)
Committed 2026-10-19 05:58 UTC
Scanned 2026-10-22 16:10 UTC 28 days ago
Coverage 206 files, 143 java
87 test files not scanned

Earlier scans of this repository

4 scans · compare any two
0 to 200 locations Already broken 1 → 0 (down 1) Quantum-vulnerable 36 → 57 (up 21) Reduced margin 17 → 46 (up 29) Could not be determined 79 → 100 (up 21) Quantum-safe 5 → 74 (up 69) The filled point is the scan you are reading.
Scanned Commit To address Key establishment
27 days ago 2a4c1d787efb develop 95 19 Compare
28 days ago this scan 2a4c1d787efb develop 92 19
28 days ago 2a4c1d787efb develop 80 21 Compare
29 days ago ef7f0b8e76b4 48 4 Compare

A repository is scanned again when someone asks: Run a fresh scan.

List of cryptographic assets

ECIES Quantum-vulnerable Recorded traffic 12 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ClientEciesEncryptor.java:147 final EciesEncryptor eciesEncryptor = new EciesEncryptor(envelopeKey, sharedInfo2);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ClientEciesEncryptor.java:151 final EciesPayload eciesPayload = eciesEncryptor.encrypt(plaintext, eciesParameters);
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ClientEciesEncryptor.java:204 final EciesDecryptor decryptor = new EciesDecryptor(envelopeKey, sharedInfo2);
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ServerEciesEncryptor.java:138 envelopeKey = new EciesEnvelopeKey(encryptorSecrets.getEnvelopeKey(), ephemeralPublicKey);
  5. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ServerEciesEncryptor.java:148 return new ServerEciesSecrets(envelopeKey.getSecretKey(), sharedInfo2Base);
  6. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ServerEciesEncryptor.java:171 envelopeKey = new EciesEnvelopeKey(encryptorSecrets.getEnvelopeKey(), ephemeralPublicKey);
  7. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ServerEciesEncryptor.java:190 final EciesDecryptor eciesDecryptor = new EciesDecryptor(envelopeKey, sharedInfo2);
  8. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ServerEciesEncryptor.java:196 final byte[] plaintext = eciesDecryptor.decrypt(eciesPayload);
  9. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ServerEciesEncryptor.java:227 final EciesEncryptor eciesEncryptor = new EciesEncryptor(envelopeKey, sharedInfo2);
  10. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/ServerEciesEncryptor.java:231 final EciesPayload eciesPayload = eciesEncryptor.encrypt(plaintext, eciesParameters);
  11. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/EncryptorFactory.java:75 final ClientEncryptor<EciesEncryptedRequest, EciesEncryptedResponse> encryptor = new ClientEciesEncryptor(encryptorId, encryptorParameters);
  12. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/EncryptorFactory.java:128 final ServerEncryptor<EciesEncryptedRequest, EciesEncryptedResponse> encryptor = new ServerEciesEncryptor(encryptorId, encryptorParameters);
code.named-call
ECDSA Quantum-vulnerable 10 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/activation/PowerAuthClientActivation.java:98 return SIGNATURE_UTILS.validateECDSASignature(EcCurve.P256, bytes, signature, masterPublicKey);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/activation/PowerAuthClientActivation.java:133 return SIGNATURE_UTILS.validateECDSASignature(EcCurve.P384, bytes, signature, masterPublicKey);
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/activation/PowerAuthClientActivation.java:177 return HybridPublicKeyFingerprint.computeEcdsaFingerprint(((ECPublicKey) devicePublicKey), (ECPublicKey) serverPublicKey, activationId, ActivationVersion.VERSION_4);
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:84 final Signature ecdsa = Signature.getInstance(curve.getEcdsaAlgorithm(), PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  5. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:113 final Signature ecdsa = Signature.getInstance(curve.getEcdsaAlgorithm(), PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  6. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:142 return this.validateECDSASignature(EcCurve.P256, signedBytes, signature, masterPublicKey);
  7. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:159 final Signature ecdsa = Signature.getInstance(curve.getEcdsaAlgorithm(), PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  8. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/activation/PowerAuthServerActivation.java:99 return SIGNATURE_UTILS.computeECDSASignature(EcCurve.P256, bytes, masterPrivateKey);
  9. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/v4/activation/PowerAuthServerActivation.java:131 return SIGNATURE_UTILS.computeECDSASignature(EcCurve.P384, bytes, masterPrivateKey);
  10. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/v4/activation/PowerAuthServerActivation.java:246 return HybridPublicKeyFingerprint.computeEcdsaFingerprint(((ECPublicKey) devicePublicKey), (ECPublicKey) serverPublicKey, activationId, ActivationVersion.VERSION_4);
code.named-call
DSA Quantum-vulnerable 3 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

code.named-call
EC Quantum-vulnerable 3 places See details

Classical key material handled through the JCA

`KeyFactory.getInstance()` for a classical algorithm. This indicates the code parses or produces keys of that family, which is a migration surface even where it does no cryptography itself.

A quantum computer of sufficient size breaks this completely. It has to be replaced, not tuned. An elliptic-curve key pair. The source does not say whether it signs or agrees a shared secret, and the curve alone cannot: the same curve serves both.

What to do. Include this code path in the inventory: it has to accept post-quantum key encodings before the keys themselves can change.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/KeyConvertor.java:133 return KeyFactory.getInstance("EC", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME).generatePublic(pubSpec);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/KeyConvertor.java:184 return KeyFactory.getInstance("EC", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME).generatePublic(pubSpec);
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/KeyConvertor.java:241 return KeyFactory.getInstance("EC", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME).generatePrivate(ecPrivateKeySpec);
java.keyfactory · CWE-327
ECIES Quantum-vulnerable Recorded traffic 3 places See details

Algorithm implemented in the repository

A class named for the algorithm it is, rather than one that calls a library: NTLM's `class MD4`, a bundled `class Sha256`, `class SCrypt`, `class Ed25519Java`. Cryptography the project carries itself is cryptography nobody else patches.

This project carries its own copy of an encryption or hashing method.

What to do. Prefer the platform's or a maintained library's implementation, and record why this one exists if it has to stay.

code.implementation
ECDH Quantum-vulnerable Recorded traffic 2 places See details

Classical key pair generated through the JCA

`KeyPairGenerator.getInstance()` with a classical algorithm. The concrete family and, where an `initialize()` call is close enough to read, the key size are resolved from the source and reported on the finding.

A quantum computer of sufficient size breaks this completely. It has to be replaced, not tuned. Broken by Shor's algorithm on a cryptographically relevant quantum computer.

What to do. Generate the classical key alongside an ML-KEM or ML-DSA key and carry both until relying parties accept the post-quantum one.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:81 final KeyPairGenerator kpg = KeyPairGenerator.getInstance("EC", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:83 return kpg.generateKeyPair();
java.keypairgenerator · CWE-327
ECDH Quantum-vulnerable Recorded traffic 2 places See details

Classical key agreement through the JCA

`KeyAgreement.getInstance()` with ECDH, DH or XDH. Key agreement is the highest-priority class of finding: traffic recorded today is decrypted once the key exchange is broken.

A quantum computer of sufficient size breaks this completely. It has to be replaced, not tuned. Broken by Shor's algorithm on a cryptographically relevant quantum computer.

What to do. ML-KEM-768 (FIPS 203), or a hybrid X25519+ML-KEM-768 construction that keeps the classical guarantee while adding the quantum one.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:103 KeyAgreement keyAgreement = KeyAgreement.getInstance("ECDH", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:106 final byte[] sharedSecret = keyAgreement.generateSecret();
java.keyagreement · CWE-327
ECDSA Quantum-vulnerable 2 places See details

Classical signature algorithm through the JCA

`Signature.getInstance()` with a classical algorithm. The digest and the key algorithm are split out of the JCA name, so `SHA1withRSA` reports both the broken digest and the quantum-vulnerable key.

A quantum computer of sufficient size breaks this completely. It has to be replaced, not tuned. Broken by Shor's algorithm on a cryptographically relevant quantum computer.

What to do. ML-DSA-65 (FIPS 204). Where the verifier cannot be changed, sign twice and publish both signatures.

java.signature · CWE-327
AES Reduced margin 11 places See details

Cipher transformation named away from the call

A JCA transformation string - `algorithm/mode/padding` - written somewhere other than a `getInstance()` argument, which is how a codebase that centralises its cryptography passes the choice to a helper. The string is unambiguous wherever it appears: nothing but a transformation is spelled that way.

This names an encryption method as text, and passes it to code elsewhere that does the work. It is the same choice, made in a different place.

What to do. The same migration applies as to the call that consumes it. Move the constant and the call together, so the inventory keeps naming the algorithm after the change.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/activation/PowerAuthClientActivation.java:174 final byte[] statusBlob = aes.decrypt(cStatusBlob, iv, transportKey, "AES/CBC/NoPadding");
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/vault/PowerAuthClientVault.java:49 private static final String AES_TRANSFORMATION = "AES/CBC/PKCS7Padding";
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/vault/PowerAuthClientVault.java:71 final byte[] ciphertext = AES_UTILS.encrypt(privateKeyBytes, iv, vaultEncryptionKey, AES_TRANSFORMATION);
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/vault/PowerAuthClientVault.java:90 final byte[] ciphertext = AES_UTILS.encrypt(privateKeyBytes, iv, vaultEncryptionKey, AES_TRANSFORMATION);
  5. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/vault/PowerAuthClientVault.java:113 byte[] keyBytes = AES_UTILS.decrypt(ciphertext, iv, vaultEncryptionKey, AES_TRANSFORMATION);
  6. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/vault/PowerAuthClientVault.java:135 byte[] keyBytes = AES_UTILS.decrypt(ciphertext, iv, vaultEncryptionKey, AES_TRANSFORMATION);
  7. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/AESEncryptionUtils.java:82 return this.encrypt(bytes, iv, secret, "AES/CBC/PKCS7Padding");
  8. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/AESEncryptionUtils.java:125 return this.decrypt(bytes, iv, secret, "AES/CBC/PKCS7Padding");
  9. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/encryptor/aead/Aead.java:71 final byte[] encrypted = aes.encrypt(plaintext, iv, keyEncryption, "AES/CTR/NoPadding");
  10. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/encryptor/aead/Aead.java:102 return aes.decrypt(encrypted, iv, keyEncryption, "AES/CTR/NoPadding");
  11. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/activation/PowerAuthServerActivation.java:173 return new AESEncryptionUtils().encrypt(statusBlob, iv, transportKey, "AES/CBC/NoPadding");
java.transformation · CWE-327
AES Reduced margin 10 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/activation/PowerAuthClientActivation.java:172 final AESEncryptionUtils aes = new AESEncryptionUtils();
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/vault/PowerAuthClientVault.java:53 private static final AESEncryptionUtils AES_UTILS = new AESEncryptionUtils();
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/vault/PowerAuthClientVault.java:66 AESEncryptionUtils aes = new AESEncryptionUtils();
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/vault/PowerAuthClientVault.java:83 AESEncryptionUtils aes = new AESEncryptionUtils();
  5. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/vault/PowerAuthClientVault.java:101 AESEncryptionUtils aes = new AESEncryptionUtils();
  6. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/EciesDecryptor.java:45 private final AESEncryptionUtils aes = new AESEncryptionUtils();
  7. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/EciesEncryptor.java:49 private final AESEncryptionUtils aes = new AESEncryptionUtils();
  8. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:217 AESEncryptionUtils aes = new AESEncryptionUtils();
  9. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/encryptor/aead/Aead.java:47 private static final AESEncryptionUtils aes = new AESEncryptionUtils();
  10. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/vault/PowerAuthServerVault.java:75 AESEncryptionUtils aes = new AESEncryptionUtils();
code.named-call
AES Reduced margin From a constant 4 places See details

Classical public-key cipher through the JCA

`Cipher.getInstance()` with a transformation whose algorithm component is a public-key or legacy symmetric cipher. The transformation string is parsed into algorithm, mode and padding, so `RSA/ECB/PKCS1Padding` is separated from `RSA/ECB/OAEPWithSHA-256AndMGF1Padding`.

A quantum computer weakens this but does not break it. Increasing the key or digest size restores the margin. Grover's algorithm halves the effective strength; the parameter, not the design, is the problem. The key size was not visible at this call site, so the weaker case is assumed.

What to do. For RSA encryption, move to ML-KEM-768 and keep RSA-OAEP only as the classical half of a hybrid during transition.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/AESEncryptionUtils.java:57 Cipher cipherForCryptoResponse = Cipher.getInstance(transformation, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/AESEncryptionUtils.java:59 return cipherForCryptoResponse.doFinal(bytes);
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/AESEncryptionUtils.java:100 Cipher cipherForCryptoResponse = Cipher.getInstance(transformation, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/AESEncryptionUtils.java:102 return cipherForCryptoResponse.doFinal(bytes);
java.cipher · CWE-327
SHA-256 Reduced margin 4 places See details

Hash algorithm through the JCA

`MessageDigest.getInstance()`. MD5 and SHA-1 are reported as already broken; SHA-256 is reported as a reduced margin rather than a defect.

A quantum computer weakens this but does not break it. Increasing the key or digest size restores the margin. Pre-image resistance falls to about 128 bits of quantum work. Adequate for most uses; SHA-384 restores the full margin where a signature must last decades.

What to do. SHA-256 as the floor, SHA-384 where the digest protects something that must remain verifiable for decades.

java.messagedigest · CWE-328
SHA-256 Reduced margin 3 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

code.named-call
AES Reduced margin 1 place See details

Algorithm named in a setting

A setting whose name says it holds an algorithm, given a literal that names one: `withOaepPaddingDigestAlgorithm("SHA-512")`, `signatureAlgorithm = "SHA256withRSA"`, `"digestAlgorithm": "SHA-256"`. The algorithm never reaches a `getInstance()` in this file - it is carried to one somewhere else, often through configuration - so a scan that only reads the factories cannot see it at all.

Something here is configured to use a named algorithm. The code that uses it may be somewhere else entirely, but this is the line that decides which algorithm it is.

What to do. Find what consumes the setting. The migration belongs to that operation; this line is where the choice is actually written down, and usually where it is easiest to change.

config.algorithm-setting · CWE-327
AES Reduced margin 1 place See details

Key material constructed for a named algorithm

`new SecretKeySpec(bytes, "AES")` and the other key-spec constructors name the algorithm as an argument rather than through `getInstance()`. Code that wraps raw bytes into a key this way often never calls `getInstance()` at all, so the algorithm is invisible to a scan that only looks at the factories.

This wraps raw bytes into a key for a named algorithm. It is part of the same migration as whatever uses that key.

What to do. Wherever this key is used, the same migration applies as to the call that consumes it. Trace it to the operation and treat the two together.

java.keyspec · CWE-327
PBKDF2 Reduced margin 1 place See details

Key material constructed for a named algorithm

`new SecretKeySpec(bytes, "AES")` and the other key-spec constructors name the algorithm as an argument rather than through `getInstance()`. Code that wraps raw bytes into a key this way often never calls `getInstance()` at all, so the algorithm is invisible to a scan that only looks at the factories.

This wraps raw bytes into a key for a named algorithm. It is part of the same migration as whatever uses that key.

What to do. Wherever this key is used, the same migration applies as to the call that consumes it. Trace it to the operation and treat the two together.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:294 PBEKeySpec spec = new PBEKeySpec(password.toCharArray(), salt, iterations, 128);
java.keyspec · CWE-327
SHA3-256 Reduced margin 1 place See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

code.named-call
PBKDF2-HMAC-SHA1 Reduced margin 2 places See details

Password hashing or key derivation

A `SecretKeyFactory` for PBKDF2, or a BouncyCastle password KDF. Not a quantum exposure, and part of a complete inventory.

This is how passwords are stored. Quantum computers do not meaningfully weaken it.

What to do. PBKDF2 needs a high iteration count. Argon2 through BouncyCastle is stronger.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:295 SecretKeyFactory skf = SecretKeyFactory.getInstance("PBKDF2WithHmacSHA1", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:296 byte[] keyBytes = skf.generateSecret(spec).getEncoded();
java.kdf
unknown Could not be determined 14 places See details

Algorithm chosen at runtime

`KeyPairGenerator.getInstance(x)`, `Mac.getInstance(lookup(key))` and the other JCA factories, where the argument is a variable or a call. The algorithm cannot be resolved without running the program, so this is reported as an unknown rather than assumed to be classical; what the factory does - sign, tag, digest - is still reported, and so are the lines that use the object.

This code picks its encryption method while it runs, so a scan cannot tell which one it ends up using. Somebody has to check the configuration.

What to do. Trace the value to its configuration source and record the concrete algorithm in the cryptographic inventory by hand.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/totp/Totp.java:285 final Mac hmac = Mac.getInstance(algorithm, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/totp/Totp.java:288 return hmac.doFinal(data);
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/HMACHashUtilities.java:101 final Mac mac = Mac.getInstance(algorithm, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/HMACHashUtilities.java:103 return mac.doFinal(data);
  5. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:84 final Signature ecdsa = Signature.getInstance(curve.getEcdsaAlgorithm(), PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  6. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:87 return ecdsa.sign();
  7. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:113 final Signature ecdsa = Signature.getInstance(curve.getEcdsaAlgorithm(), PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  8. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:116 return ecdsa.sign();
  9. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:159 final Signature ecdsa = Signature.getInstance(curve.getEcdsaAlgorithm(), PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  10. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/SignatureUtils.java:162 return ecdsa.verify(signature);
  11. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsaKeyConvertor.java:75 final KeyFactory keyFactory = KeyFactory.getInstance(algorithmName, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  12. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsaKeyConvertor.java:101 final KeyFactory keyFactoryMlDsa = KeyFactory.getInstance(algorithmName, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  13. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKemKeyConvertor.java:88 final KeyFactory keyFactory = KeyFactory.getInstance(algorithmName, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  14. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKemKeyConvertor.java:102 final KeyFactory keyFactory = KeyFactory.getInstance(algorithmName, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
java.keypairgenerator.variable · CWE-327
unknown Could not be determined 5 places See details

Key material constructed for a named algorithm

`new SecretKeySpec(bytes, "AES")` and the other key-spec constructors name the algorithm as an argument rather than through `getInstance()`. Code that wraps raw bytes into a key this way often never calls `getInstance()` at all, so the algorithm is invisible to a scan that only looks at the factories.

This wraps raw bytes into a key for a named algorithm. It is part of the same migration as whatever uses that key.

What to do. Wherever this key is used, the same migration applies as to the call that consumes it. Trace it to the operation and treat the two together.

java.keyspec · CWE-327
unknown Could not be determined 1 place See details

Cryptographic library in the dependency manifest

A dependency known to implement classical asymmetric cryptography. Its presence is inventory, not a finding about this codebase: the library may never be called with a quantum-vulnerable algorithm.

The project depends on a cryptography library. Listed so the inventory is complete; it is not by itself a problem.

What to do. Check the version. Several of these libraries have shipped ML-KEM and ML-DSA support since 2024, so the migration may need an upgrade rather than a replacement.

  1. powerauth-java-crypto/pom.xml:60 <artifactId>nimbus-jose-jwt</artifactId>
dep.crypto-library
HMAC Quantum-safe 14 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/EciesDecryptor.java:46 private final HMACHashUtilities hmac = new HMACHashUtilities();
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/EciesEncryptor.java:50 private final HMACHashUtilities hmac = new HMACHashUtilities();
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/EciesEnvelopeKey.java:63 private static final HMACHashUtilities hmac = new HMACHashUtilities();
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:241 HMACHashUtilities hmac = new HMACHashUtilities();
  5. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:263 HMACHashUtilities hmac = new HMACHashUtilities();
  6. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/AuthenticationCodeLegacyUtils.java:134 final HMACHashUtilities hmac = new HMACHashUtilities();
  7. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/EciesUtils.java:136 return new HMACHashUtilities().hash(transportKey, applicationSecretBytes);
  8. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/HashBasedCounterUtils.java:92 final SecretKey ctrDataHashKey = keyGenerator.deriveSecretKeyHmac(transportCtr, ctrData);
  9. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/KeyDerivationUtils.java:90 final SecretKey ivKey = keyGenerator.deriveSecretKeyHmac(transportIv, ivData);
  10. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/TokenUtils.java:41 private static final HMACHashUtilities HMAC = new HMACHashUtilities();
  11. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/TokenUtils.java:116 digest = HMAC.hash(tokenSecret, data);
  12. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/TokenUtils.java:120 digest = HMAC.hash(tokenSecret, data);
  13. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/util/DataDigest.java:83 private final HMACHashUtilities hmac = new HMACHashUtilities();
  14. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/v4/util/DataDigest.java:84 private final HMACHashUtilities hmac = new HMACHashUtilities();
code.named-call
ML-DSA-65 Quantum-safe 5 places See details

Post-quantum algorithm through BouncyCastle

A `org.bouncycastle.pqc` class. This is migration work already in progress and is recorded so the inventory shows what has been done, not only what is outstanding.

This is already a quantum-safe algorithm. It is listed so the report shows the work that has been completed.

What to do. None. Confirm the parameter set matches the required NIST category.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/client/v4/activation/PowerAuthClientActivation.java:66 pqcDsaMlL3 = new MlDsa(MLDSAParameterSpec.ml_dsa_65);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/util/HybridPublicKeyFingerprint.java:69 public static String computeHybridFingerprint(SharedSecretAlgorithm sharedSecretAlgorithm, ECPublicKey ecDevicePublicKey, MLDSAPublicKey pqcDevicePublicKey, ECPublicKey ecServerPublicKey, MLDSAPublicKey pqcServerPublicKey, String activation
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsa.java:38 private final MLDSAParameterSpec dsaParameterSpec;
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/model/context/SharedSecretAlgorithm.java:89 public MLDSAParameterSpec getMlDsaParameterSpec() {
  5. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/server/v4/activation/PowerAuthServerActivation.java:64 pqcDsaMlL3 = new MlDsa(MLDSAParameterSpec.ml_dsa_65);
java.bouncycastle.pqc
Argon2 Quantum-safe 4 places See details

Password hashing or key derivation

A `SecretKeyFactory` for PBKDF2, or a BouncyCastle password KDF. Not a quantum exposure, and part of a complete inventory.

This is how passwords are stored. Quantum computers do not meaningfully weaken it.

What to do. PBKDF2 needs a high iteration count. Argon2 through BouncyCastle is stronger.

java.kdf
ML-DSA-65 Quantum-safe 4 places See details

Classical signature algorithm through the JCA

`Signature.getInstance()` with a classical algorithm. The digest and the key algorithm are split out of the JCA name, so `SHA1withRSA` reports both the broken digest and the quantum-vulnerable key.

No known quantum attack changes how strong this is. No known quantum algorithm changes the security margin.

What to do. ML-DSA-65 (FIPS 204). Where the verifier cannot be changed, sign twice and publish both signatures.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsa.java:80 final Signature mlDsa = Signature.getInstance("MLDSA", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsa.java:83 return mlDsa.sign();
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsa.java:102 final Signature mlDsa = Signature.getInstance("MLDSA", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsa.java:105 return mlDsa.verify(signature);
java.signature · CWE-327
ML-KEM-768 Quantum-safe 4 places See details

Classical public-key cipher through the JCA

`Cipher.getInstance()` with a transformation whose algorithm component is a public-key or legacy symmetric cipher. The transformation string is parsed into algorithm, mode and padding, so `RSA/ECB/PKCS1Padding` is separated from `RSA/ECB/OAEPWithSHA-256AndMGF1Padding`.

No known quantum attack changes how strong this is. No known quantum algorithm changes the security margin.

What to do. For RSA encryption, move to ML-KEM-768 and keep RSA-OAEP only as the classical half of a hybrid during transition.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKem.java:82 final KeyGenerator keyGenerator = KeyGenerator.getInstance("ML-KEM", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKem.java:84 return (SecretKeyWithEncapsulation) keyGenerator.generateKey();
  3. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKem.java:100 final KeyGenerator keyGenerator = KeyGenerator.getInstance("ML-KEM", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  4. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKem.java:102 return keyGenerator.generateKey();
java.cipher · CWE-327
Argon2i Quantum-safe 3 places See details

Algorithm named by a constant

A library or project constant whose name is an algorithm, used in code: `JavaAlgorithm.SHA256`, `XMLCipher.AES_128`, Go `crypto.SHA256` and `x509.SHA256WithRSA`, `SignatureMethod.RSA_SHA256`. The holder's name has to say it holds algorithms, so an unrelated `Foo.AES` is left alone.

This line picks an algorithm by name.

What to do. The migration belongs to the operation that consumes the constant; this line is where the choice is written down.

code.algorithm-constant
HMAC-SHA256 Quantum-safe 3 places See details

Message authentication code through the JCA

`Mac.getInstance()`. HMAC is not broken by Shor and is only marginally affected by Grover; it is inventoried, not flagged, unless the underlying digest is broken.

This is a fingerprint used to prove a message was not altered. Quantum computers do not break it.

What to do. No action beyond avoiding HmacMD5 and HmacSHA1.

java.mac
ML-KEM-768 Quantum-safe 3 places See details

Post-quantum algorithm through BouncyCastle

A `org.bouncycastle.pqc` class. This is migration work already in progress and is recorded so the inventory shows what has been done, not only what is outstanding.

This is already a quantum-safe algorithm. It is listed so the report shows the work that has been completed.

What to do. None. Confirm the parameter set matches the required NIST category.

java.bouncycastle.pqc
Argon2 Quantum-safe 2 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

code.named-call
HMAC-SHA256 Quantum-safe 2 places See details

Algorithm named by a constant

A library or project constant whose name is an algorithm, used in code: `JavaAlgorithm.SHA256`, `XMLCipher.AES_128`, Go `crypto.SHA256` and `x509.SHA256WithRSA`, `SignatureMethod.RSA_SHA256`. The holder's name has to say it holds algorithms, so an unrelated `Foo.AES` is left alone.

This line picks an algorithm by name.

What to do. The migration belongs to the operation that consumes the constant; this line is where the choice is written down.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/totp/Totp.java:78 return generateTotp(key, countTimeSteps(instant, stepLength), digitsNumber, Algorithm.HMAC_SHA256.code);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/totp/Totp.java:136 return validateTotp(otp, key, instant, digitsNumber, steps, stepLength, Algorithm.HMAC_SHA256.code);
code.algorithm-constant
HMAC-SHA384 Quantum-safe 2 places See details

Message authentication code through the JCA

`Mac.getInstance()`. HMAC is not broken by Shor and is only marginally affected by Grover; it is inventoried, not flagged, unless the underlying digest is broken.

This is a fingerprint used to prove a message was not altered. Quantum computers do not break it.

What to do. No action beyond avoiding HmacMD5 and HmacSHA1.

java.mac
HMAC-SHA512 Quantum-safe 2 places See details

Algorithm named by a constant

A library or project constant whose name is an algorithm, used in code: `JavaAlgorithm.SHA256`, `XMLCipher.AES_128`, Go `crypto.SHA256` and `x509.SHA256WithRSA`, `SignatureMethod.RSA_SHA256`. The holder's name has to say it holds algorithms, so an unrelated `Foo.AES` is left alone.

This line picks an algorithm by name.

What to do. The migration belongs to the operation that consumes the constant; this line is where the choice is written down.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/totp/Totp.java:105 return generateTotp(key, countTimeSteps(instant, stepLength), digitsNumber, Algorithm.HMAC_SHA512.code);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/totp/Totp.java:167 return validateTotp(otp, key, instant, digitsNumber, steps, stepLength, Algorithm.HMAC_SHA512.code);
code.algorithm-constant
KMAC Quantum-safe From a constant 2 places See details

Message authentication code through BouncyCastle

A BouncyCastle MAC: `HMac` over a digest, `CMac` or `GMac` over a block cipher, `Poly1305`. The digest or cipher it is built on is read from the construction, so `new HMac(new SHA256Digest())` is HMAC-SHA-256.

This checks that data has not been tampered with. Quantum computers do not break it.

What to do. No change of algorithm is needed; keep keys at 256 bits.

java.bouncycastle.mac
ML-DSA-65 Quantum-safe 2 places See details

JOSE algorithm declared in configuration

An `alg` value in JSON or YAML. `none` is reported as a critical defect; HS* is an HMAC and is not quantum-vulnerable; RS*, PS*, ES* and EdDSA are.

No known quantum attack changes how strong this is. No known quantum algorithm changes the security margin.

What to do. No standardised post-quantum JOSE algorithm exists yet. Keep token lifetimes short.

jose.algorithm · CWE-327
ML-DSA-65 Quantum-safe 2 places See details

Classical key pair generated through the JCA

`KeyPairGenerator.getInstance()` with a classical algorithm. The concrete family and, where an `initialize()` call is close enough to read, the key size are resolved from the source and reported on the finding.

No known quantum attack changes how strong this is. No known quantum algorithm changes the security margin.

What to do. Generate the classical key alongside an ML-KEM or ML-DSA key and carry both until relying parties accept the post-quantum one.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsa.java:62 final KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance("MLDSA", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlDsa.java:64 return keyPairGenerator.generateKeyPair();
java.keypairgenerator · CWE-327
ML-DSA-87 Quantum-safe 2 places See details

JOSE algorithm declared in configuration

An `alg` value in JSON or YAML. `none` is reported as a critical defect; HS* is an HMAC and is not quantum-vulnerable; RS*, PS*, ES* and EdDSA are.

No known quantum attack changes how strong this is. No known quantum algorithm changes the security margin.

What to do. No standardised post-quantum JOSE algorithm exists yet. Keep token lifetimes short.

jose.algorithm · CWE-327
ML-KEM-768 Quantum-safe 2 places See details

Classical key pair generated through the JCA

`KeyPairGenerator.getInstance()` with a classical algorithm. The concrete family and, where an `initialize()` call is close enough to read, the key size are resolved from the source and reported on the finding.

No known quantum attack changes how strong this is. No known quantum algorithm changes the security margin.

What to do. Generate the classical key alongside an ML-KEM or ML-DSA key and carry both until relying parties accept the post-quantum one.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKem.java:67 final KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance("ML-KEM", PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/v4/ml/MlKem.java:69 return keyPairGenerator.generateKeyPair();
java.keypairgenerator · CWE-327
X9.63-KDF Quantum-safe From a constant 2 places See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/EciesEnvelopeKey.java:104 byte[] secretKey = KdfX9_63.derive(keyConvertor.convertSharedSecretKeyToBytes(ephemeralSecretKey), info1Data, ENVELOPE_KEY_SIZE);
  2. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/encryptor/ecies/EciesEnvelopeKey.java:135 byte[] secretKey = KdfX9_63.derive(keyConvertor.convertSharedSecretKeyToBytes(ephemeralSecretKey), info1Data, ENVELOPE_KEY_SIZE);
code.named-call
Argon2d Quantum-safe 1 place See details

Algorithm named by a constant

A library or project constant whose name is an algorithm, used in code: `JavaAlgorithm.SHA256`, `XMLCipher.AES_128`, Go `crypto.SHA256` and `x509.SHA256WithRSA`, `SignatureMethod.RSA_SHA256`. The holder's name has to say it holds algorithms, so an unrelated `Foo.AES` is left alone.

This line picks an algorithm by name.

What to do. The migration belongs to the operation that consumes the constant; this line is where the choice is written down.

code.algorithm-constant
Argon2id Quantum-safe 1 place See details

Algorithm named by a constant

A library or project constant whose name is an algorithm, used in code: `JavaAlgorithm.SHA256`, `XMLCipher.AES_128`, Go `crypto.SHA256` and `x509.SHA256WithRSA`, `SignatureMethod.RSA_SHA256`. The holder's name has to say it holds algorithms, so an unrelated `Foo.AES` is left alone.

This line picks an algorithm by name.

What to do. The migration belongs to the operation that consumes the constant; this line is where the choice is written down.

code.algorithm-constant
CSPRNG Quantum-safe From a constant 1 place See details

Random number generation

`SecureRandom`. A platform CSPRNG is not a quantum exposure; it is recorded because an inventory that omits the randomness source is incomplete. `SHA1PRNG` is named explicitly where it appears, since it is a legacy algorithm even though its output is adequate.

This is where the software gets its random numbers. Quantum computers do not weaken it.

What to do. No action. Prefer the platform default over naming an algorithm.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/generator/KeyGenerator.java:166 random = SecureRandom.getInstance(SECURE_RANDOM_ALGORITHM_NAME, PowerAuthConfiguration.CRYPTO_PROVIDER_NAME);
java.rng
HMAC-SHA1 Quantum-safe 1 place See details

Algorithm implemented in the repository

A class named for the algorithm it is, rather than one that calls a library: NTLM's `class MD4`, a bundled `class Sha256`, `class SCrypt`, `class Ed25519Java`. Cryptography the project carries itself is cryptography nobody else patches.

This project carries its own copy of an encryption or hashing method.

What to do. Prefer the platform's or a maintained library's implementation, and record why this one exists if it has to stay.

code.implementation
HMAC-SHA1 Quantum-safe 1 place See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

  1. powerauth-java-crypto/src/main/java/com/wultra/security/powerauth/crypto/lib/totp/Totp.java:202 final byte[] expectedOtp = generateTotp(key, step, otp.length, algorithm);
code.named-call
HMAC-SHA512 Quantum-safe 1 place See details

Message authentication code through the JCA

`Mac.getInstance()`. HMAC is not broken by Shor and is only marginally affected by Grover; it is inventoried, not flagged, unless the underlying digest is broken.

This is a fingerprint used to prove a message was not altered. Quantum computers do not break it.

What to do. No action beyond avoiding HmacMD5 and HmacSHA1.

java.mac
SHA3-384 Quantum-safe 1 place See details

Call to code named for an algorithm

A call, construction or operation whose own name states the algorithm: a project's wrapper such as `Hash.sha256(data)`, `hmacSha256(key, msg)`, `getMD5()` or `new ScryptGenerator(..)`, a key type such as `new Ed25519PublicKey(bytes)`, or an operation on an object named for its algorithm, `sha256.digest()`. The library call inside the wrapper is reported where it is written; these are the places it is used.

This line calls code named after an encryption or hashing method.

What to do. Migrate the wrapper once, and these call sites follow it.

code.named-call
X9.63-KDF Quantum-safe 1 place See details

Algorithm implemented in the repository

A class named for the algorithm it is, rather than one that calls a library: NTLM's `class MD4`, a bundled `class Sha256`, `class SCrypt`, `class Ed25519Java`. Cryptography the project carries itself is cryptography nobody else patches.

This project carries its own copy of an encryption or hashing method.

What to do. Prefer the platform's or a maintained library's implementation, and record why this one exists if it has to stay.

code.implementation

Cryptographic assets

Algorithm Assessment What it means Occurrences
unknown Could not be determined The algorithm could not be established from the source - chosen at runtime, or decided somewhere this scan does not reach. 104
AES Reduced margin Grover's algorithm halves the effective strength; the parameter, not the design, is the problem. The key size was not visible at this call site, so the weaker case is assumed. 27
HMAC Quantum-safe A keyed MAC is not affected by Shor and only marginally by Grover. 26
RSA Quantum-vulnerable Broken by Shor's algorithm on a cryptographically relevant quantum computer. 20
ECIES Quantum-vulnerable Broken by Shor's algorithm on a cryptographically relevant quantum computer. 15
ML-DSA-65 Quantum-safe No known quantum algorithm changes the security margin. 13
ECDSA Quantum-vulnerable Broken by Shor's algorithm on a cryptographically relevant quantum computer. 12
Argon2 Quantum-safe The current recommended password hashing function. Not affected by Shor, and memory-hard against Grover. 11
ML-KEM-768 Quantum-safe No known quantum algorithm changes the security margin. 9
SHA-256 Reduced margin Pre-image resistance falls to about 128 bits of quantum work. Adequate for most uses; SHA-384 restores the full margin where a signature must last decades. 7
ECDH Quantum-vulnerable Broken by Shor's algorithm on a cryptographically relevant quantum computer. 4
EC Quantum-vulnerable An elliptic-curve key pair. The source does not say whether it signs or agrees a shared secret, and the curve alone cannot: the same curve serves both. 3
DSA Quantum-vulnerable Broken by Shor's algorithm on a cryptographically relevant quantum computer. 3
PBKDF2 Reduced margin Not broken by a quantum computer, but weak against modern GPU cracking at low iteration counts, which is a present-day concern. 3
X9.63-KDF Quantum-safe No known quantum algorithm changes the security margin. 3
KMAC Quantum-safe No known quantum algorithm changes the security margin. 2
ML-DSA-87 Quantum-safe No known quantum algorithm changes the security margin. 2
CSPRNG Quantum-safe A cryptographically secure random number generator provided by the platform. Not weakened by a quantum computer. 1
SHA3-256 Reduced margin Grover's algorithm halves the effective strength; the parameter, not the design, is the problem. 1
SHA3-384 Quantum-safe No known quantum algorithm changes the security margin. 1

Imported cryptographic libraries

Library Files
org.bouncycastle BouncyCastle, whose low-level API bypasses the JCA algorithm strings. It has shipped ML-KEM and ML-DSA since 1.79 20
javax.crypto the JCE 54