@profullstack/threatcrush 0.8.0 → 0.9.0

package/dist/index.js

@@ -9998,6 +9998,56 @@ var CODE_RULES = [
     severity: "high",
     pattern: /(?:token|secret|password|salt|nonce|session|otp|reset|apikey|api_key)[\w]*\s*[:=][^;\n]{0,60}(?:Math\s*\.\s*random\s*\(|\brandom\s*\.\s*(?:random|randint|choice)\s*\(|\brand\s*\()/i
   },
+  // ── Weak crypto: Python ──────────────────────────────────────────────────
+  //
+  // The generic rules above catch the credential case on the matched line.
+  // These cover what they miss in Python, where the security role of a value is
+  // set by the enclosing function rather than a same-line assignment — a
+  // `random`-drawn token that is *returned*, an MD5 used to *verify* an
+  // artifact — and the broken ciphers, which have no safe use at all.
+  {
+    id: "py-broken-cipher",
+    title: "broken cipher or ECB mode",
+    consequence: "DES, RC2, RC4 and Blowfish are broken or too small to rely on, and ECB encrypts identical plaintext blocks to identical ciphertext, so structure in the data survives encryption. None of them provides the confidentiality their use implies.",
+    cwe: "CWE-327",
+    severity: "high",
+    languages: ["python"],
+    // PyCryptodome/PyCrypto constructors. The mode matters only for AES, whose
+    // safe modes (GCM, CTR, CBC) are common — so AES matches solely on ECB,
+    // while DES/RC4/Blowfish are broken by the algorithm regardless of mode.
+    pattern: /\b(?:DES|DES3|ARC2|RC2|ARC4|RC4|Blowfish|XOR)\s*\.\s*new\s*\(|\bAES\s*\.\s*new\s*\([^)\n]*\bMODE_ECB\b/,
+    inherent: true,
+    guard: false
+  },
+  {
+    id: "py-weak-hash",
+    title: "broken hash algorithm",
+    consequence: "MD5 and SHA-1 have practical collisions, so a digest used for integrity or a signature can be forged to match a value the code trusts.",
+    cwe: "CWE-327",
+    severity: "medium",
+    languages: ["python"],
+    pattern: /\bhashlib\s*\.\s*(?:md5|sha1)\s*\(/,
+    // Python 3.9+ marks a non-security digest — a cache key, an ETag — with
+    // `usedforsecurity=False`, which is exactly the "this MD5 is not a security
+    // claim" signal, so it exempts the line rather than being flagged.
+    lineGuard: /usedforsecurity\s*=\s*False/
+  },
+  {
+    id: "py-predictable-random-seed",
+    title: "PRNG seeded from a predictable value",
+    consequence: "Seeding `random` from the clock or the process id makes its whole sequence reproducible, so anything drawn from it afterwards \u2014 a token, an id, a shuffle \u2014 can be regenerated by guessing the seed.",
+    cwe: "CWE-338",
+    severity: "high",
+    languages: ["python"],
+    // A time- or pid-derived seed, which is the predictable kind. A fixed
+    // integer seed (`random.seed(42)`) is deliberate reproducibility for tests
+    // and simulations, so it is left alone. This needs no credential context:
+    // seeding the global PRNG from the clock is a weakness on its own terms,
+    // which is why the enclosing function's name — that this engine does not
+    // read as evidence anyway — is not consulted.
+    pattern: /\brandom\s*\.\s*seed\s*\([^)\n]*(?:time\s*\.\s*time|datetime|\.\s*now\s*\(|getpid)/,
+    inherent: true
+  },
   {
     id: "redos-nested-quantifier",
     title: "regex with nested unbounded quantifiers",