Skip to content
Open
Show file tree
Hide file tree
Changes from 8 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions internal/encryption/cipher.go
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,23 @@ func (c *Cipher) Decrypt(ciphertextAndTag, aad []byte, keyID uint32, nonce []byt
return plaintext, nil
}

// LoadedKeyIDs returns the sorted list of key_ids currently loaded in
// the underlying keystore. Used by the storage layer's rebadge guard
// (PR742 codex P1 family) to trial-decrypt a cleartext-labelled body
// against every candidate DEK — rotation leaves multiple DEKs active
// at once, and the on-disk envelope's key_id field can be rewritten
// by an attacker, so the guard must iterate rather than trust it.
//
// Returns nil for a nil receiver or zero-value Cipher; callers
// MUST NOT treat that as "no keys" without considering the
// surrounding context.
func (c *Cipher) LoadedKeyIDs() []uint32 {
if c == nil || c.keystore == nil {
return nil
}
return c.keystore.IDs()
}

// aeadFor validates keyID and nonce length, then returns the
// pre-initialized AEAD from the keystore. The hot path here is a single
// atomic.Pointer load + a map lookup; AES key expansion happened once
Expand Down
284 changes: 284 additions & 0 deletions store/encryption_glue.go
Original file line number Diff line number Diff line change
@@ -0,0 +1,284 @@
package store

import (
"github.com/bootjp/elastickv/internal/encryption"
"github.com/cockroachdb/errors"
)

// ErrEncryptedReadIntegrity wraps encryption.ErrIntegrity for storage-layer
// callers (Get / scan / iterator). Per design §4.1, callers MUST treat this
// as a typed read error and never silently zero the value or skip the row.
//
// Callers can disambiguate it from any other read error with errors.Is.
var ErrEncryptedReadIntegrity = errors.New("store: encrypted value failed integrity check (GCM tag mismatch); refusing to surface plaintext")

// NonceFactory produces unique 12-byte AES-GCM nonces for the storage
// envelope (§4.1). The factory is responsible for the cluster-wide
// uniqueness invariant across `(node_id, local_epoch, write_count)` —
// the storage layer just calls Next() and uses what comes back.
//
// Stage 7 of the encryption rollout will replace the in-tree
// reference implementation (deterministicCounterNonce, defined in the
// _test.go helper) with a writer-registry-backed factory that
// guarantees uniqueness across voters, learners, and historical
// replicas. The interface stays the same; only the construction
// changes. Implementations MUST NOT return the same nonce twice
// under the same DEK — AES-GCM nonce reuse is catastrophic
// (see encryption.Cipher doc).
type NonceFactory interface {
Next() ([encryption.NonceSize]byte, error)
}

// ActiveStorageKeyID reports the currently-active storage DEK
// identifier. The bool is false when no storage DEK is active (i.e.
// the cluster has not run Phase 1 of the §7.1 rollout yet) — in that
// case the storage layer writes cleartext as if no cipher were
// configured. Stage 5/6 wires this from the sidecar's Active.Storage
// slot; Stage 2 takes it as a closure so test code can flip it
// independently.
type ActiveStorageKeyID func() (uint32, bool)

// WithEncryption configures the pebble-backed store to wrap every
// committed value in the §4.1 storage envelope.
//
// All three arguments must be non-nil. activeKeyID is called on
// every Put — when it returns ok=false the store writes cleartext
// (encryption_state = 0b00) even though a cipher is wired, matching
// the §7.1 Phase 0 / Phase 1 split where capability is provisioned
// before activation. Reads that observe encryption_state = 0b01
// always go through the cipher regardless of activeKeyID, so a
// cluster mid-cutover stays readable.
//
// Calling WithEncryption with any nil argument is a no-op (the
// store stays in legacy cleartext-only mode). This keeps the
// option backwards-compatible with every existing NewPebbleStore
// caller and keeps the Stage 2 wiring trivially reversible.
func WithEncryption(cipher *encryption.Cipher, nf NonceFactory, activeKeyID ActiveStorageKeyID) PebbleStoreOption {
return func(s *pebbleStore) {
if cipher == nil || nf == nil || activeKeyID == nil {
return
}
s.cipher = cipher
s.nonceFactory = nf
s.activeStorageKeyID = activeKeyID
}
}

// encryptForKey wraps plaintext in the §4.1 storage envelope when an
// encryption key is active for the storage purpose. Returns
// (plaintext, encStateCleartext, nil) when encryption is disabled or
// no DEK is currently active so the cipher=nil fast path stays a
// single branch.
//
// AAD binds the ciphertext to:
//
// - the envelope header (envelope_version, flag, key_id),
// - the encoded Pebble key (defeats cut-and-paste / version
// substitution per §4.1 case 2/3),
// - the on-disk value-header bytes (tombstone bit,
// encryption_state, expireAt). Without binding the value-header,
// a disk attacker could flip the tombstone bit or lower expireAt
// to force GetAt/scan into a silent ErrKeyNotFound/expired
// branch BEFORE any AEAD verification runs (PR742 codex P1).
//
// The expireAt argument is the value the caller will write into the
// resulting storage entry; tombstone is hard-coded false because the
// encrypt path is never invoked for tombstone writes (deletes carry
// no plaintext and are emitted as cleartext by the store
// already).
func (s *pebbleStore) encryptForKey(pebbleKey, plaintext []byte, expireAt uint64) ([]byte, byte, error) {
if s.cipher == nil || s.activeStorageKeyID == nil {
return plaintext, encStateCleartext, nil
}
keyID, ok := s.activeStorageKeyID()
if !ok {
return plaintext, encStateCleartext, nil
}
nonceArr, err := s.nonceFactory.Next()
if err != nil {
return nil, 0, errors.Wrap(err, "store: nonce factory")
}
nonce := nonceArr[:]
// flag = 0: Snappy compression deferred to Stage 9 per design §4.1.
const envelopeFlag byte = 0
var hdr [valueHeaderSize]byte
writeValueHeaderBytes(hdr[:], false /*tombstone*/, expireAt, encStateEncrypted)
aad := buildStorageAAD(encryption.EnvelopeVersionV1, envelopeFlag, keyID, hdr[:], pebbleKey)
ciphertextAndTag, err := s.cipher.Encrypt(plaintext, aad, keyID, nonce)
if err != nil {
return nil, 0, errors.Wrap(err, "store: encrypt value")
}
env := encryption.Envelope{
Version: encryption.EnvelopeVersionV1,
Flag: envelopeFlag,
KeyID: keyID,
Nonce: nonceArr,
Body: ciphertextAndTag,
}
encoded, err := env.Encode()
if err != nil {
return nil, 0, errors.Wrap(err, "store: encode envelope")
}
return encoded, encStateEncrypted, nil
Comment on lines +117 to +121
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Enforce snapshot-size limit after envelope encoding

Encrypted writes can exceed the restore-time value length cap even when validateValueSize succeeds: encryptForKey adds envelope overhead and returns bytes that are stored as-is, but restore still caps each raw value at maxSnapshotValueSize + valueHeaderSize in readRestoreEntry. With encryption enabled, a plaintext near maxSnapshotValueSize is writable yet its native snapshot restore fails with ErrValueTooLarge, so the system can persist data that cannot be recovered via snapshot. Please either validate post-encryption size here or raise the restore bound for encrypted rows.

Useful? React with 👍 / 👎.

}

// decryptForKey is the read-side counterpart. encState=0 returns the
// body verbatim (with the envelope-shaped fingerprint check below);
// encState=1 decodes the envelope, recomputes the AAD (header +
// value-header + pebble key), and unwraps via the cipher. A GCM tag
// mismatch surfaces as ErrEncryptedReadIntegrity — callers MUST NOT
// silently translate this into "key not found" or "empty value"
// because that would let a disk attacker who flipped a tag bit (or
// any AAD-bound header field) silently corrupt reads.
//
// Reserved encryption_state values are rejected upstream in
// decodeValue, so this function only sees the two valid states.
//
// Cleartext-rebadge guard (PR742 codex P1, round-3). A disk
// attacker who flips encryption_state from 0b01 to 0b00 leaves the
// envelope bytes in place but tells the read path to skip
// decryption — so the caller would silently receive raw envelope
// bytes as "plaintext". When a cipher is wired, we therefore run
// the body through DecodeEnvelope on the cleartext branch too: if
// it parses as a well-formed envelope AND its key_id is loaded in
// the keystore (i.e. the bytes are almost certainly a relabeled
// envelope rather than a coincidence), we reject as
// ErrEncryptedReadIntegrity. False positives on legitimate
// cleartext are bounded by the joint probability of envelope-shape
// match + a 32-bit key_id collision with a loaded DEK.
//
// sv is the storedValue freshly decoded from the on-disk bytes; its
// Tombstone, ExpireAt, and EncState are reproduced into the AAD so
// any flip on disk fails GCM verification. Callers MUST run
// tombstone / expireAt visibility checks AFTER decrypt succeeds —
// the values they observe pre-decrypt are not yet authenticated.
func (s *pebbleStore) decryptForKey(pebbleKey []byte, sv storedValue, body []byte) ([]byte, error) {
if sv.EncState == encStateCleartext {
if err := s.rejectRebadgedEnvelope(pebbleKey, sv, body); err != nil {
return nil, err
}
return body, nil
Comment on lines +144 to +148
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reject encrypted rows relabeled as cleartext

When decryptForKey sees encStateCleartext, it returns the body without any envelope/tag verification. A disk attacker (or bit-flip corruption) can change an encrypted row’s header bits from 0b01 to 0b00, causing reads to return raw envelope bytes as if they were legitimate plaintext instead of surfacing ErrEncryptedReadIntegrity. This is a fail-open integrity bypass for encrypted-at-rest data because the authentication check is skipped entirely once the header is relabeled.

Useful? React with 👍 / 👎.

}
if s.cipher == nil {
return nil, errors.New("store: encrypted value present but no cipher configured")
}
env, err := encryption.DecodeEnvelope(body)
if err != nil {
return nil, errors.Wrap(err, "store: decode envelope")
}
var hdr [valueHeaderSize]byte
writeValueHeaderBytes(hdr[:], sv.Tombstone, sv.ExpireAt, sv.EncState)
aad := buildStorageAAD(env.Version, env.Flag, env.KeyID, hdr[:], pebbleKey)
plain, err := s.cipher.Decrypt(env.Body, aad, env.KeyID, env.Nonce[:])
if err != nil {
if errors.Is(err, encryption.ErrIntegrity) {
return nil, errors.Wrap(
errors.WithSecondaryError(ErrEncryptedReadIntegrity, err),
"store: decrypt value")
}
return nil, errors.Wrap(err, "store: decrypt value")
}
// AES-GCM Open returns a nil dst slice for an empty plaintext;
// upstream callers (notably ExistsAt) distinguish "key absent"
// from "key present with empty value" via val != nil. Normalize
// to a non-nil zero-length slice so an empty stored value
// continues to satisfy ExistsAt → true (PR742 codex P1 round-4).
if plain == nil {
plain = []byte{}
}
return plain, nil
}

// rejectRebadgedEnvelope is the cleartext-branch guard for the §4.1
// encState rebadge attack. The on-disk encryption_state bit is not
// itself authenticated (PR742 codex P1 family — Stage 8 plans to
// move it into authenticated MVCC metadata), so a disk attacker who
// flips it from 0b01 to 0b00 leaves the original envelope bytes in
// place and tells the read path to skip decryption. Without a
// guard, the caller would silently receive raw envelope bytes as
// "plaintext".
//
// The detection runs an actual AEAD trial decrypt: rebuild the
// AAD that the envelope WOULD have used had it been written under
// encState=0b01, then call cipher.Decrypt over the parsed envelope
// body. If the GCM tag verifies the bytes are unambiguously a
// real envelope — only the holder of the DEK can produce a tag
// that survives this check, so legitimate cleartext data has a
// 2⁻¹²⁸ false-positive probability (negligible). On any other
// outcome (parse failure, unknown key, tag mismatch) we treat the
// row as legitimate cleartext.
//
// PR742 review history:
// - round-3: "envelope-shape AND key_id loaded" — bypassable via
// key_id rewrite to an unloaded value (codex round-4).
// - round-5: "envelope-shape only" — false-positives on
// legitimate binary cleartext that happens to start with 0x01
// and parse the length/version/flag/nonce checks (codex
// round-6).
// - round-7 (this change): tag verification under reconstructed
// encrypted-state AAD — no false positives, catches the
// primary key_id-unchanged rebadge. The kid-rewrite-to-loaded-
// other-DEK variant still falls through (AAD mismatch on the
// foreign DEK), but the user observes ciphertext garbage that
// application code rejects downstream rather than plaintext —
// deferred to Stage 8.
//
// No-op when the store has no cipher wired (legacy single-mode
// deployments cannot have rebadge attacks) or when the body is too
// short to be an envelope.
func (s *pebbleStore) rejectRebadgedEnvelope(pebbleKey []byte, sv storedValue, body []byte) error {
if s.cipher == nil {
return nil
}
if len(body) < encryption.EnvelopeOverhead {
return nil
}
env, err := encryption.DecodeEnvelope(body)
if err != nil {
// Body does not parse as an envelope; treat as legitimate
// cleartext.
return nil //nolint:nilerr // intentional: parse failure means "not an envelope"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Fail closed when relabeled envelope decoding fails

rejectRebadgedEnvelope treats any DecodeEnvelope failure as legitimate cleartext, so an attacker can flip encryption_state to cleartext and corrupt one envelope header byte (for example version) to force this branch and bypass integrity checks. In that case decryptForKey returns raw ciphertext bytes instead of ErrEncryptedReadIntegrity, which is a fail-open path for encrypted-at-rest data because KV values are opaque and callers may accept those bytes as valid application data.

Useful? React with 👍 / 👎.

}
// Reconstruct the AAD as if the row carried encState=encrypted
// and trial-decrypt under each loaded DEK. The encrypt-time AAD
// included the *original* envelope key_id; attackers can rewrite
// that field on disk, so we substitute each candidate kid into
// the AAD's HeaderAAD section rather than trusting env.KeyID.
// Other AAD components (Tombstone, ExpireAt, pebbleKey) are
// already AAD-bound from the encrypt path; any flip there shifts
// the AAD and trips the tag mismatch below regardless of which
// DEK we try.
var hdr [valueHeaderSize]byte
writeValueHeaderBytes(hdr[:], sv.Tombstone, sv.ExpireAt, encStateEncrypted)
for _, kid := range s.cipher.LoadedKeyIDs() {
aad := buildStorageAAD(env.Version, env.Flag, kid, hdr[:], pebbleKey)
if _, err := s.cipher.Decrypt(env.Body, aad, kid, env.Nonce[:]); err == nil {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reject relabeled envelopes when header fields are modified

rejectRebadgedEnvelope rebuilds trial-decrypt AAD from sv.Tombstone/sv.ExpireAt, which come from the attacker-controlled cleartext-labeled header. If an attacker flips encryption_state to cleartext and changes tombstone/expiry bits, every trial decrypt sees the wrong AAD and fails, so this function returns nil and the read path serves ciphertext bytes (or silently returns not-found/expired) instead of ErrEncryptedReadIntegrity. This recreates a fail-open tamper path for encrypted rows under disk-byte modification.

Useful? React with 👍 / 👎.

return errors.Wrap(ErrEncryptedReadIntegrity,
"store: cleartext-labelled value verifies as a relabeled envelope under a loaded DEK")
}
}
// No loaded DEK produces a tag match — body is either legitimate
// cleartext that happens to look envelope-shaped, an envelope
// under a retired DEK, or a partially-tampered envelope. The
// first case is the legitimate-mixed-mode outcome the round-6
// codex finding required us to preserve.
return nil
}

// buildStorageAAD composes the §4.1 storage-envelope AAD with a
// single allocation. Layout:
//
// envelope_version ‖ flag ‖ key_id ‖ value_header(9B) ‖ pebble_key
//
// Pre-sizing avoids the double-allocation gemini medium flagged on
// PR742 round-1 (AppendHeaderAADBytes alloc + the subsequent
// append). The value-header inclusion was added in round-2 in
// response to the codex P1 finding that flipping tombstone / expireAt
// would otherwise bypass GCM verification.
func buildStorageAAD(version, flag byte, keyID uint32, header, pebbleKey []byte) []byte {
aad := make([]byte, 0, encryption.HeaderAADSize+len(header)+len(pebbleKey))
aad = encryption.AppendHeaderAADBytes(aad, version, flag, keyID)
aad = append(aad, header...)
aad = append(aad, pebbleKey...)
return aad
}
52 changes: 52 additions & 0 deletions store/encryption_test_helpers.go
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
package store

import (
"encoding/binary"
"sync/atomic"

"github.com/bootjp/elastickv/internal/encryption"
)

// CounterNonceFactory is a test-only NonceFactory that produces the
// design §4.1 deterministic nonce shape (`node_id ‖ local_epoch ‖
// write_count`) without the writer-registry round-trip Stage 7
// brings. Production wiring uses the registry-backed factory; this
// implementation is only safe for tests where the caller controls
// every node_id / local_epoch combination.
//
// Exposed (vs. living in a *_test.go file) so the encryption
// integration tests in other packages can build on the same
// implementation without re-deriving the byte layout. It is
// nevertheless test-grade — the doc comment on NonceFactory
// emphasises that production callers MUST guarantee
// (node_id, local_epoch, write_count) uniqueness.
type CounterNonceFactory struct {
nodeID uint16
localEpoch uint16
writes atomic.Uint64
}

// NewCounterNonceFactory constructs a CounterNonceFactory pinned to
// the given (nodeID, localEpoch). write_count starts at 0 and
// monotonically increments on every Next().
func NewCounterNonceFactory(nodeID, localEpoch uint16) *CounterNonceFactory {
return &CounterNonceFactory{nodeID: nodeID, localEpoch: localEpoch}
}

// Next produces the next 12-byte nonce. Layout matches design §4.1:
//
// bytes 0-1 node_id (big-endian uint16)
// bytes 2-3 local_epoch (big-endian uint16)
// bytes 4-11 write_count (big-endian uint64)
//
// Big-endian is chosen so a hex dump of consecutive nonces is
// human-readable as a counter; the AAD does NOT include the nonce
// bytes (the cipher composes the nonce into AES-GCM directly), so
// the byte order is internal to the factory.
func (f *CounterNonceFactory) Next() ([encryption.NonceSize]byte, error) {
var n [encryption.NonceSize]byte
binary.BigEndian.PutUint16(n[0:2], f.nodeID)
binary.BigEndian.PutUint16(n[2:4], f.localEpoch)
binary.BigEndian.PutUint64(n[4:12], f.writes.Add(1))
return n, nil
}
Loading
Loading