Graph
Tiny Encryption Algorithm

🍵Tiny Encryption Algorithm

NEW

Also known as: TEA

A simple, fast symmetric block cipher with 64-bit blocks and a 128-bit key, known to have cryptographic weaknesses that inspired XTEA and XXTEA.

DESCRIPTION

The Tiny Encryption Algorithm (TEA) is a compact Feistel-based block cipher created by David Wheeler and Roger Needham. It operates on 64-bit blocks with a 128-bit key and is implemented with very small code size. TEA became popular for embedded systems and low-resource environments. However, it suffers from key equivalence and related-key attacks, leading to improved variants XTEA and XXTEA. TEA is not recommended for new designs but still appears in legacy software and educational contexts. When encountered, use secure modes and consider migrating to stronger ciphers like AES or at least XTEA/XXTEA if constrained.

ALTERNATIVE DEFINITIONS

University of Cambridge

TEA is a Feistel cipher with 64 rounds, a block size of 64 bits, and a 128-bit key.

Concise technical characterization from the original authors.

Source

Wikipedia

The Tiny Encryption Algorithm (TEA) is a block cipher notable for its simple structure, small code size, and speed, but suffers from several weaknesses.

Highlights trade-off between simplicity and cryptanalytic weaknesses.

Source

Feistel Function Symmetric Block Cipher Algorithms Differential Cryptanalysis Embedded Systems Key Schedule RC5 CTR Mode Cipher Block Chaining

COMPETING TERMS

XTEA XXTEA Rijndael

RELATIONS

KNOWLEDGE AREAS

Data Security Software Engineering

TARGET AUDIENCE

Security Architect Cybersecurity Engineer Software Developer DevOps Engineer

EXTERNAL SOURCES

TOP QUESTIONS

Why was the Tiny Encryption Algorithm created?

TEA was designed for simplicity and compactness, enabling fast encryption in constrained environments like embedded systems.

Category: Origin

Is the Tiny Encryption Algorithm secure for new systems?

No. Known weaknesses make TEA unsuitable for new deployments; AES or at least XTEA/XXTEA should be preferred.

Category: Risks

What replaced the Tiny Encryption Algorithm?

XTEA and XXTEA were introduced to address weaknesses; however, AES remains the modern standard for most applications.

Category: Alternatives

Where is the Tiny Encryption Algorithm still encountered?

It appears in legacy codebases, older mobile apps, and educational examples illustrating Feistel ciphers.

Category: Usage

What is the biggest misconception about the Tiny Encryption Algorithm?

That simplicity equals security; while elegant, TEA’s design has exploitable properties under certain attack models.

Category: Misunderstanding

How should TEA-encrypted data be handled today?

Maintain decryption for compatibility, but plan migration to AES with authenticated modes to improve security.

Category: Management

Does TEA benefit from hardware acceleration?

Generally no. TEA lacks widespread hardware acceleration, unlike AES, reducing performance advantages on modern CPUs.

Category: Performance

What mode of operation should be used with TEA if unavoidable?

Use CTR or CBC with a strong MAC, or an AEAD wrapper if available; never use ECB.

Category: BestPractices

What is a striking analogy for TEA’s design?

Think of TEA as a minimalist toolkit—light and handy—but missing specialized tools needed for modern security demands.

Category: Example