← Lab /Security & privacy

Formal security analysis performed on GKS private-key FHE scheme

Security & privacy Theory · arXiv Threat model

The claim

The GKS FHE scheme is secure under the authors' formal analysis

John Graham, Soundes Marzougui, Miloš Pavlović, Vladimir Shpilrain · arXiv Paper PDF

Published as: “GKS Fully Homomorphic Encryption: Security Analysis”

So what

The scheme offers a private-key FHE alternative with conditional ciphertext-only security, but practical deployment must address collision-harvest risks and the weak post-ideal security before it can replace lattice-based FHE in real applications.

The five-minute version

GKS private-key FHE achieves conditional single-ciphertext IND-EAV security after conditioning on the publicly observable rank, but its multi-ciphertext COA security depends on preventing same-value collisions, which are only mitigated by the not-yet-implemented Zero Collision Guarantee (ZCG). The evidence includes a proof of conditional IND-EAV and empirical checks showing no distinguisher on equal-weight ensembles, while the paper admits that post-ideal recovery security is modest and that a full ITS proof is open.

What they found 3

What undercuts it the paper’s own results

Stated limits 3

What’s new here 4

Threat model stated by the source

Adversaryexternal eavesdropper or cloud operator (Carl)
Capabilityobserves ciphertexts; cloud operator can perform homomorphic operations but has no encryption oracle or plaintext-ciphertext pairs
Assumesprivate-key architecture; plaintext and encryption stay with data owner; no public Enc oracle; no labelled (m,c) pairs are provided to the evaluator

Artifacts & methods 5

Topics

fully homomorphic encryptionprivate-key FHEidempotent ringsIND-EAVciphertext-only attack (COA)zero-pattern leakageretraction ambiguitycollision harvest attacks
← Previous Tenant isolation bypass achieved via chained cloud provider vulnerabilities