Topic starter
08/07/2026 7:09 pm
TL;DR: Seven findings and seven informational issues emerged after six days of cryptography review in Passbolt’s 2021 security audit, with high-severity gaps centred on transport-layer encryption guidance and nonce generation in GpgAuth, according to Passbolt and Cure53. The audit shows that clear security specifications matter as much as implementation quality for identity and secret-handling systems.
Editorial analysis by NHI Mgmt Group, based on content published by PassBolt: “Passbolt security audit 2021 - Part 1”.
By the numbers:
- PBL-01-001 and PBL-01-004 were marked as high severity because they covered transport layer encryption and nonce generation for authentication operations.
- Wikipedia says 2.71 quintillion random version-4 UUIDs are needed for a 50% probability of at least one collision.
Key questions
Q: What breaks when cryptographic specifications leave transport security undefined?
A: When transport security is left undefined, teams can ship deployments that depend on local judgement rather than a mandatory security baseline.
Q: Why do nonce requirements matter in challenge-based authentication?
A: Nonce requirements matter because the challenge must be unique and used once to preserve authentication integrity.
Q: How should teams evaluate whether a security specification is complete enough?
A: Teams should check whether the specification defines the security property, the allowed implementation behaviour, and the failure conditions with enough precision that different engineers would reach the same conclusion.
Practitioner guidance
- Tighten protocol requirements in the security specification Write mandatory transport, nonce, and authentication behaviour into the formal specification so implementation teams do not infer security properties from prose or defaults.
- Enforce HTTPS and cipher baseline rules at deployment Make TLS requirements explicit in installation guidance, health checks, and server administration runbooks so insecure transport cannot remain an acceptable operating mode.
- Review authentication assumptions for nonce single-use semantics Check whether challenge-response flows depend on values that are merely random rather than provably single-use, then align the protocol text with the intended security property.
Bottom line: The article’s core risk is specification ambiguity, not a demonstrated compromise of the product.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
08/07/2026 7:33 pm
Specification ambiguity is itself a security control failure: when cryptographic requirements are not written tightly enough, implementation teams inherit risk through interpretation rather than code. Passbolt’s audit summary shows that the most serious issues were omissions in the specification, not confirmed runtime exploitation. For identity and secret-handling systems, that means governance has to include the written protocol model, not just the deployed stack.
A question worth separating out:
A: They should treat the gap as a governance issue, not only an engineering task. The right response is to update the protocol contract, align implementation and deployment guidance, and carry the missing requirement into future certification and review cycles.
👉 Read our full editorial: Passbolt security audit 2021 shows specification gaps in cryptography