Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

aerospike/aerospike-client-java
master @ 8ebf34e
10
Fixes
1
CVEs
CRITICAL
Peak severity
66.7%
Coverage
Highlights
Insecure Deserialization: 3 prior fixes. Scrutinize any change in this area.
client/src/com/aerospike/client/command/Buffer.java: most-fixed (3 issues). Treat as high-risk during review.
6 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Untrusted Deserialization: Insecure deserialization of Java objects (JBLOBs) within client buffers allowed arbitrary code execution via compromised or malicious database servers. This led to the complete deprecation and removal of runtime Java deserialization capabilities in the client.
Auth Bypass: Establishing connection paths during cluster tend cycles without verifying the existence of a valid session token could allow unauthenticated command execution when authentication was ostensibly enabled.
Authentication Bypass: Implicit sign extension of signed bytes to integers in the Aerospike Admin protocol parser allowed negative result codes to misrepresent authentication states, bypassing security controls.