Graph/5ea62436-f81a-4d2e-b219-b4982b644faa

Domainunvalidated

Cryptography

5ea62436-f81a-4d2e-b219-b4982b644faa

Cryptography

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0006

Effectiveness0.000

Connections

50 linked nodes

IMPLEMENTATION_OFComponent

openssl

PERTAIN_TORootCause

if your app can read the keys, an attacker can read the keys. Tension: there is still a simple way to get them. Outcome: it does not prevent it completely.

PERTAIN_TOSolution

requires a valid account, SSL with certificate pinning — to protect your own server API calls. Outcome: This increases the difficulty for an attacker to get the keys.

PERTAIN_TOProblem

Never store private keys or the corresponding certificate files (.pfx/p12) on an unencrypted file system. — the private key files on an encrypted file system. Tension: private keys or the corresponding certificate files (.pfx/p12) on an unencrypted file system.

PERTAIN_TOProblem

The clientside storage of this key should be as secure as possible and never be sent to the server — ts encrypted data and decrypts it locally. Tension: otherwise I as the owner (or an attacker in the system) could decrypt the users database entries. Outcome: Encrypting the plain text locally and storing the ciphertext remotely is the way to go.

PERTAIN_TOProblem

I need to know if there's a way to identify if each of those individual libraries can be verified for FIPS 140-2 compliance? — crypto libraries(direct/indirect dependencies) being used in the application developed using the React Framework(JavaScript). Outcome: FIPS 140-2 compliance is not a self assessed compliance.

PERTAIN_TOSolution

If you are looking for a FIPS 140-2 compliant JavaScript Cryptographic Library — JavaScript Cryptographic Library. Tension: any other library that you may be referring to is not FIPS compliant. Outcome: Virtru is the only option available.

PERTAIN_TOSolution

pass `False` if you're not using the algorithm for security purposes. — False indicates that the hashing algorithm is not used in a security context. Tension: Insecure algorithms are enabled by default. Outcome: Python will tell OpenSSL to allow insecure algorithms anyway.

PERTAIN_TORootCause

urllib3 removed the ability to change DEFAULT_CIPHER in the major version 2.0.0 — installed urllib3 2.0.3. Tension: Removed DEFAULT_CIPHERS, HAS_SNI, USE_DEFAULT_SSLCONTEXT_CIPHERS, from the private module urllib3.util.ssl_. Outcome: the main way to get around the error.

PERTAIN_TOProblem

requests.exceptions.SSLError: [SSL: SSL_NEGATIVE_LENGTH] dh key too small (_ssl.c:600) — when using the requests library. Tension: urllib3 removed the ability to change DEFAULT_CIPHER in the major version 2.0.0. Outcome: after getting a new laptop and reinstalling my packages, I began to get the original error again.

PERTAIN_TOSolution

For urllib3 ver > 2.0.0 i use: — requests library. Tension: Preferably without having to downgrade my urllib3 to an older version. Outcome: sess.mount('https://', CustomSSLAdapter()).

PERTAIN_TOProblem

package com.igen.configlib.constant;. Outcome: This should never be stored as code in any central cvs, only is dedicated secret storages.

PERTAIN_TOSolution

This should never be stored as code in any central cvs. Outcome: only is dedicated secret storages.

PERTAIN_TOProblem

MongoDB client-side field level encryption generates a new Data Encryption Key on each run, making previously encrypted data unreadable

PERTAIN_TOSolution

Remove the key vault collection drop and reuse an existing key by checking clientEnc.GetKeyByAltName before calling CreateDataKey

PERTAIN_TOProblem

I'm trying to generate key pairs (public and private) and I'm looking for cryptographically secure libraries that allow me to generate good entropy — in a node.js environment. Tension: I wanted to use another secure module to have a single combined entropy. Outcome: or even just the crypto module is fine.

PERTAIN_TOSolution

using the `crypto` module is fine — In Node.js. Tension: instead of trying to do it yourself. Outcome: you can simply do what you're doing without concern.

PERTAIN_TOProblem

you can sniff all HTTPS communications in an unencrypted form. Tension: All fields and data from headers, request bodies, and responses are intercepted without encryption. Outcome: Traffic is encrypted to protect the user, not to protect apps from their user.

PERTAIN_TOSolution

You can limit TLS sniffing using certificate pinning. — for some situations, it's worth the trouble. Tension: Google does not recommend this because it's hard to manage. Outcome: See also HTTP Toolkit's discussion on the topic.

PERTAIN_TOProblem

That however is not a safe way to encrypt data by itself. Tension: because it doesn't include any authentication. Outcome: I would recommend either finding a high-level library that builds on top of WebCrypto.

PERTAIN_TOSolution

Browsers themselves provide an encryption interface. That interface supports AES-GCM — You mention using the private key. Tension: WebAuthn does not currently provide any symmetric key that can be used for encryption. Outcome: You would need to download Chr.

PERTAIN_TOReport

CVE-2022-0778 OpenSSL BN_mod_sqrt Infinite Loop in Tonelli-Shanks

PERTAIN_TOReport

OpenSSL CVE-2021-3711: SM2 Decryption Heap Overflow via Untrusted Length Field

PERTAIN_TOReport

CVE-2021-3711: OpenSSL SM2 Decryption Heap Overflow via sm2_plaintext_size() Miscalculation

PERTAIN_TOReport

CVE-2021-20231 GnuTLS — Use-after-free via realloc-aliasing in TLS 1.3 client_hello extensions (key_share + pre_shared_key)

PERTAIN_TOReport

CVE-2022-0778: Infinite loop in BN_mod_sqrt Tonelli-Shanks algorithm

PERTAIN_TOReport

CVE-2022-0778 — OpenSSL BN_mod_sqrt infinite loop on non-prime modulus via crafted EC certificate

PERTAIN_TOReport

CVE-2022-0778: OpenSSL BN_mod_sqrt infinite loop with composite prime modulus

PERTAIN_TOReport

CVE-2021-3711: SM2 Plaintext Size Miscalculation Leading to Heap Overflow

PERTAIN_TOReport

CVE-2023-0286: OpenSSL X.509 x400Address type confusion — ASN1_STRING decoded, read as ASN1_TYPE

PERTAIN_TORootCause

verify_token() splits the token. Tension: _sign() receives different input than what was originally signed, producing a different digest every time. Outcome: create_token() computes HMAC over raw JSON bytes.

PERTAIN_TOProblem

A heap buffer overflow in OpenSSL's SM2 decryption (CVE-2021-3711). — OpenSSL's SM2 decryption. Outcome: There is also no bounds check in sm2_decrypt before writing C2->length bytes into ptext_buf.

PERTAIN_TOSolution

Two fixes needed:. Outcome: The official patch in OpenSSL 1.1.1l does both: sm2_plaintext_size was changed to parse the input DER and use the actual C2 length.

PERTAIN_TOProblem

JWT-style tokens created with create_token() consistently fail signature verification in verify_token(), causing tests to error with “Invalid or expired token” even for freshly created tokens.

PERTAIN_TOSolution

Fix verify_token() to derive payload_bytes using bytes.fromhex(payload_hex) so the HMAC-SHA256 signature verification uses the exact same payload bytes that were originally signed in create_token().

PERTAIN_TOSolution

Fix the off-by-one at line 184 of crypto/punycode.c — OpenSSL 3.0.7 applied exactly this change. Outcome: change `if (written_out > max_out)` to `if (written_out >= max_out)`.

PERTAIN_TORootCause

the sm2_plaintext_size() function in crypto/sm2/sm2_crypt.c computes the required output buffer size using a FIXED overhead formula — ASN.1 INTEGER encoding of the EC point coordinates (C1x and C1y BIGNUMs). Tension: This is WRONG because the ASN.1 INTEGER encoding of the EC point coordinates (C1x and C1y BIGNUMs) can be SHORTER than field_size bytes. Outcome: An attacker who crafts a malicious ciphertext with intentionally small C1x/C1y INTEGER values (few bytes) but a very large C2 (payload) field will cause sm2_plaintext_size to return a buffer size smaller than the actual decoded C2->length.

PERTAIN_TOProblem

contains an infinite loop vulnerability — OpenSSL's BN_mod_sqrt function in crypto/bn/bn_sqrt.c. Tension: when processing a maliciously crafted prime. Outcome: causing a Denial of Service.

PERTAIN_TOPackage

gnutls

PERTAIN_TORootCause

Tension: may realloc its backing storage, freeing the chunk the cached pointer references.

PERTAIN_TOProblem

heap use-after-free in two TLS 1.3 client extension serializers — lib/ext/key_share.c:key_share_send_params and lib/ext/pre_shared_key.c:client_send_params. Outcome: Subsequent reads/writes through the cached alias are use-after-free.

PERTAIN_TOSolution

Never cache raw pointers into a buffer that may be reallocated.

PERTAIN_TORootCause

the main Tonelli–Shanks loop (`while (1)` starting around line 286 of bn_sqrt.c) can fail to terminate — When p is composite. Tension: its only exits are BN_is_one(b) success or the inner `if (i == e)` not-a-square error.

PERTAIN_TOProblem

any process that parses the malicious certificate. Tension: The result is an infinite loop.

PERTAIN_TOSolution

commit 3118eb6 — ensure the Tonelli–Shanks outer loop in BN_mod_sqrt cannot spin when p is composite. Tension: break out with BN_R_NOT_A_SQUARE if the inner squaring loop did not make progress. Outcome: upgrade to 1.1.1n / 3.0.2, and refuse certificates carrying explicit EC parameters in favor of named curves.

PERTAIN_TOAlgorithm

Tonelli-Shanks

PERTAIN_TOSolution

The fix is to add a maximum iteration counter to the outer Tonelli-Shanks loop to prevent infinite loops when given invalid input parameters. — OpenSSL's patch adds a check to limit the maximum number of iterations of the outer while loop. Tension: a reasonable limit would be the number of bits in the prime (or a constant multiple thereof). Outcome: Additionally, stronger validation of the prime `p` parameter would help prevent this attack vector.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info