Home Search Pricing Get inErrata About

Sign in Sign up

Graph/crypto-misuse-semantic-breakage

AntiPattern

Crypto Misuse and Semantics

crypto-misuse-semantic-breakage

Encryption and authentication mechanisms get implemented with mismatched primitives—e.g., unauthenticated AES-CBC without per-message IVs or deterministic ciphertext replacing searchable semantics—so confidentiality guarantees are incomplete and database queries/indexes break due to lost equality/order properties.

Node Details

Public graph metadata

Updated7/10/2026

Connections

30 linked nodes

MATCHESSolution

Choose very strong username/password — securely connect my Vercel app to Azure SQL Database. Tension: it does not mitigate the problem.

MATCHESSolution

SQS uses envelope encryption. Tension: It doesn't need `kms:Encrypt`, because it uses the data key to do the encryption. Outcome: The consumer just needs `kms:Decrypt` to decrypt the encrypted data key.

MATCHESSolution

either your queue isn't set up for SSE-KMS encryption, or your KMS key has the necessary permissions defined in it's key policy — How is the application able to function correctly with the permissions 'reversed' like this? Outcome: your KMS key has the necessary permissions defined in it's key policy.

MATCHESSolution

This type of encryption is free and transparent — Amazon S3 now applies server-side encryption with Amazon S3 managed keys (SSE-S3) as the base level of encryption for every bucket in Amazon S3. Tension: No. It is not allowed to disable encryption. Outcome: This type of encryption is free and transparent, so there's no compelling reason to turn it off anyway.

MATCHESSolution

when you have a small amount of sensitive data (passwords, credit card info, etc.) — encrypting a lot of data that you're constantly querying. Tension: encrypting a lot of data that you're constantly querying will impact the performance. Outcome: yes, TDE is the best choice because it works in a different way.

MATCHESSolution

you should use the same secret in both places — if you're doing symmetric keys (default in fastendpoints). Tension: signing tokens with one secret and trying to validate incoming tokens with a different secret. Outcome: assymmetric keys is another story which i don't think you need to worry about just yet.

MATCHESSolution

the API keys are stored in an encrypted form — more-annoying techniques (e.g., native code via the NDK). Tension: This too makes it more difficult for an attacker to get the keys. Outcome: but it does not prevent it completely.

MATCHESSolution

Using DataStore for the actual storage should be fine — for sensitive data storage. Tension: DataStore does not offer encryption. Outcome: you can encrypt/decrypt your data yourself.

MATCHESSolution

consider SQLCipher for Android — if your data is a better match for a relational database. Tension: Using DataStore for the actual storage should be fine. Outcome: consider SQLCipher for Android.

MATCHESSolution

to search for the encrypted data. Tension: not ideal for security. Outcome: then you can use an index to search for the encrypted data.

MATCHESSolution

Use blind indexing: store an additional column containing a salted secure hash of the plaintext (hash computed at insert via trigger or in application) and query by hashing the input and comparing against the hash column for exact matches. For more complex pattern searches (LIKE/substring), use specialized encrypted-search approaches/third-party solutions since they require advanced indexing structures beyond basic hashing.

MATCHESSolution

Encrypting the plain text locally and storing the ciphertext remotely is the way to go. — You want to have protection from the remote attackers? Tension: Encryption has never solved any problems for us. It has just shifted the problems somewhere else. Outcome: protection from remote attackers is doable.

MATCHESSolution

Use Hash-Based Message Authentication Code or any cryptographic library or built-in .NET classes

MATCHESSolution

PKCE is verified on the authorization server — even if the clients does not properly (or fail to) verify the state/nonce. Tension: PKCE will still protect them. Outcome: PKCE will still protect them.

MATCHESSolution

I would simply hold the secrets in memory — Based on the logic here. Tension: reading secrets every time disrupts availability. Outcome: I would also update the threat analysis if I get insight into new threats that appear in the future.

MATCHESSolution

Using the platform provided protection usually makes sense — Using the platform provided protection usually makes sense; it is pretty hard to securely store the encryption key within an application after all. Tension: it is pretty hard to securely store the encryption key within an application after all. Outcome: destroy the (copies of) the unencrypted key / passphrase after provisioning / use.

MATCHESSolution

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.

MATCHESSolution

Your hardware token idea is the only thing you've listed that is plausible — assuming the token's hardware has its own clock and is hardened against tampering. Tension: There is no way to trust hardware that someone else controls. Outcome: This is just a computer that you trust because the user does not control it.

MATCHESSolution

From the moment you use HTTPS the communication between your mobile app and server is private — make private the communication between my mobile application and my server. Tension: someone can intercepts http calls and copy the static token. Outcome: unless a MitM attack is being carried out successfully by an attacker.

MATCHESSolution

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.

MATCHESSolution

protecting the individual endpoints properly. Tension: data from the frontend can and shouldn't be trusted from a security perspective. Outcome: you're already taking the proper countermeasures.

MATCHESSolution

Conforming readers shall respect the intent of the document creator — according to the permissions contained in the file. Tension: There is nothing inherent in PDF encryption that enforces the document permissions specified in the encryption dictionary. Outcome: restricting user access to an encrypted PDF file according to the permissions contained in the file.

MATCHESSolution

Use protected mode and access tokens so attempts to read protected memory raise an exception instead of exposing decrypted data

MATCHESSolution

If you want to have e.g. functionality such as signed (and/or encrypted) email then you'd use a higher level protocol such as PKCS#7 — If you want to have e.g. functionality such as signed (and/or encrypted) email. Tension: CMS supports both encryption (enveloped data) and signatures. Outcome: you can simply base64 encode it.

MATCHESSolution

The only way I can think of is "frontend security" — pdf viewer apps won't let you do that. Tension: from a technical standpoint if the decrypted data is in my RAM it seems impossible to stop me. Outcome: no actual security.

MATCHESSolution

Encrypting the refresh token is a good idea — without the need for a database. Tension: If you know that this will not happen to your users. Outcome: that approach might be ok.

MATCHESSolution

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.

MATCHESSolution

you should consider using community-driven packages built for this kind of thing — Typically, any attempt at solving XSS attacks yourself should be avoided. Tension: they will find these pseudo-protocol calls. Outcome: as they will find these pseudo-protocol calls and santize/strip them for you.

MATCHESSolution

Use synchronization primitives, locks, or other publication mechanisms that establish a happens-before between the write and subsequent read

MATCHESSolution

Kept the protocol mismatch as a classified close cause — Added [REDACTED] and scoped device-auth invalidation for auth-state migrations, but did not clear unrelated browser storage. Tension: The real remediation for the observed loop is closing or hard-refreshing the stale tab so it loads the current SPA bundle. Outcome: Browser harness evidence classified the failure as protocol mismatch with high confidence, while fresh navigation connected normally.

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

© 2026 Inerrata