[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-AVCEvOaZ9cY3ickTXtEbMmO9I8YAtoSjFveFzkoWjg":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":44},"2ee3645c-7844-47df-b999-eaf42ccc0750","buggy-workaround-script-caused-emudhra-to-issue-cryptographically-weak-certificates","fcf71de4-5177-4d94-9b6c-e123131884c7","Buggy Workaround Script Caused eMudhra to Issue Cryptographically Weak Certificates","eMudhra, a trusted certificate authority, issued digital certificates with critically weak single-byte private keys because a custom Python script incorrectly truncated key values during generation. The root cause was a decision to substitute a homegrown script for a proper Hardware Security Module (HSM) — the gold-standard tooling required for certificate issuance — after claiming supply chain constraints made HSMs unavailable. This matters enormously because certificates issued by a CA form the backbone of public trust on the internet; weak keys can be trivially broken, undermining the security of every relying party. The incident demonstrates that operational workarounds in cryptographic pipelines must never bypass mandatory controls, and that supply chain constraints are not an acceptable justification for weakening fundamental security guarantees.","**Immediate actions:**\n- Revoke all certificates issued using the flawed script and reissue them with properly generated keys and compliant tooling.\n- Audit all custom scripts involved in cryptographic operations and validate their output against expected key-strength parameters before use.\n\n**Long-term improvements:**\n- Establish a strict policy that certificate issuance processes may only use audited, standards-compliant HSMs or validated cryptographic libraries — no custom workarounds.\n- Build a supplier redundancy plan for critical hardware (such as HSMs) so that supply chain disruptions cannot pressure teams into unsafe substitutions.\n- Implement mandatory code review and automated testing for any script touching cryptographic material, with output validation against minimum key-length requirements.\n\n**Detection measures:**\n- Deploy automated certificate linting and validation checks (e.g., using tools like certlint or zlint) on every certificate before issuance to catch weak keys.\n- Establish continuous monitoring of issued certificates against cryptographic policy baselines and alert on anomalies such as abnormally small key sizes.",[12,13,14,15,16],"NIST SP 800-53 SC-12: Cryptographic Key Establishment and Management","NIST SP 800-53 SA-10: Developer Configuration Management","ISO\u002FIEC 27001:2022 A.8.24: Use of cryptography","NIS2 Article 21(2)(h)","NIS2 Article 21(2)(d)",{"NIS2 Article 21(2)(d)":18,"NIS2 Article 21(2)(h)":19,"ISO\u002FIEC 27001:2022 A.8.24: Use of cryptography":20,"NIST SP 800-53 SA-10: Developer Configuration Management":21,"NIST SP 800-53 SC-12: Cryptographic Key Establishment and Management":22},"NIS2's supply chain security point requires managing security risks in supplier relationships, and eMudhra's failure to maintain HSM availability through supplier diversification directly enabled the unsafe workaround.","NIS2's cryptography point requires entities to implement adequate policies on cryptography and encryption, which would have prohibited the use of an unvalidated script as a substitute for compliant cryptographic hardware.","This control requires the use of cryptography in accordance with established rules and standards, which eMudhra breached by substituting a non-compliant homegrown script for proper HSM-based key generation.","SA-10 requires that developers control and document changes to software and scripts used in security-relevant processes, which would have caught the truncation bug before the script was used in production.","SC-12 requires that cryptographic keys be generated, protected, and managed using approved mechanisms — using a buggy custom script instead of an HSM directly violates this control.","published","2026-11-12T05:20:20.688236+00:00","2026-11-12T05:20:20.672+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.theregister.com\u002Fsecurity\u002F2026\u002F11\u002F12\u002Fdisgraced-former-ca-emudhra-blames-buggy-script-for-hopelessly-weak-certificates\u002F5309244","disgraced-former-ca-emudhra-blames-buggy-script-for-hopelessly-weak-certificates-812f87","Disgraced former CA eMudhra blames buggy script for hopelessly weak certificates",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"859cf0ad-a7e9-42bb-a75d-bac6511fa5d5","Configuration Management","configuration-management","Misconfigs, default credentials, exposed services","#eab308",{"id":38,"name":39,"slug":40,"description":41,"color":42},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[],[45,49,53],{"slug":46,"name":47,"problem":48},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":50,"name":51,"problem":52},"encryption-key-management","Encryption and key management","Stolen data stays unreadable, and the keys stay under your control.",{"slug":54,"name":55,"problem":56},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]