CyberKit

Hash Collision

Also called Collision.

Two different inputs producing the same hash digest.

What it is

A situation where two distinct inputs map to an identical hash output. Collisions exist for every hash by the pigeonhole principle, but a secure hash makes finding one computationally infeasible.

Why it matters

Practical collisions break the guarantees that signatures and integrity checks depend on. They let an attacker substitute a malicious file for a benign one that shares the same digest, which is exactly why MD5 and SHA-1 were retired.

In practice

Two crafted documents with matching MD5 digests, so a signature over one silently validates the other.

What to look for

  • Two different files with the same MD5 or SHA-1 digest.
  • Certificates or signatures still relying on SHA-1.
  • Deduplication or allowlists keyed on weak hashes.

Common mistake

Thinking collisions only matter in theory. Practical MD5 and SHA-1 collisions have been used in real attacks.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • OpenSSL Open source

    The command line toolkit for inspecting certificates, keys and TLS connections.

  • HashiCorp Vault Source available

    Manages secrets and encryption keys, and can encrypt data as a service.

  • AWS Key Management Service Cloud service

    AWS's managed service for creating and controlling encryption keys.

Read next

  • Cryptographic Hash Function: A one-way function mapping any input to a fixed-size fingerprint.
  • MD5: A fast but cryptographically broken 128-bit hash, deprecated for security.
  • Digital Signature: A cryptographic proof of a message's origin and integrity.

Sources