LoginSign Up
← Back to all sparks
A

Aerospike

DEVOPS
Velocity5.0

Real time distributed NoSQL database for high throughput workloads

aerospike.com ↗

Aerospike shipped a coordinated CVE train across four release branches in one afternoon

nosql-databasecve-remediationmulti-branch-releasesmsgpack-parsingbackportscommunity-edition
◆Current state
On 16 July Aerospike published seven releases in under two hours, spanning the 7.1, 7.2, 8.0 and 8.1 branches, all carrying the same two waves of security fixes. The first wave — path traversal in UDF filename handling, an integer overflow in the msgpack size calculator, and a heap buffer overflow from missing op-size validation in batch writes — came with three numbered security bulletins. The second wave covered an out-of-bounds read in msgpack integer comparison, a memory leak on malformed proxy requests, and filter expressions bypassing validation on list and map values.
◆Where it's heading
The pattern is a vendor with long-lived enterprise deployments treating branch parity as a hard requirement: every fix is labelled with the editions it affects, and Community Edition receives the same security content as Enterprise and Federal. Most of the disclosed issues sit in msgpack parsing and collection data types, which is where untrusted client input first meets the server — a concentration that suggests a focused audit of that boundary rather than scattered reports. Outside the security work, releases are small: log verbosity, lock contention on cold-start eviction, transaction object-count accuracy.
◆Prediction
Several CVEs in this train are still marked pending assignment, so expect follow-up releases as those are published and any related parsing paths are closed out. The branch-parity discipline shown here makes it likely that whatever lands next will again ship simultaneously across all four supported lines.

◆Recent moves

  1. 24d ago

    Aerospike 8.1.2.2 fixes UDF path traversal and batch heap overflow

    The 8.1 branch's carrier for the first CVE wave: UDF filename path traversal, a msgpack size-calculator integer overflow accepting truncated structures, and a heap buffer overflow in batch writes, each with its own security bulletin. Note the feed timestamps this a few seconds after 8.1.2.3, so the ordering here does not match version order.

    View source ↗
  2. 24d ago

    Aerospike 8.1.2.3 fixes filter-expression validation bypass

    The second wave on the 8.1 branch: list and map values bypassing validation in filter expressions, a memory leak when a proxy target receives malformed or oversized requests, and an out-of-bounds read comparing msgpack integers. It also carries an Enterprise-only crash fix for MRT monitor transactions when security is enabled.

    View source ↗
  3. 24d ago

    Aerospike 8.0.0.18 backports the msgpack and proxy-leak fixes

    The same AER-6925, AER-6926 and AER-6930 fixes as 8.1.2.3, delivered to the 8.0 branch nine minutes earlier. The accompanying bug fixes are branch-specific — a dump-wb-summary command rejection and a use_mounts leak on pmem initialization error paths.

    View source ↗
  4. 24d ago

    Aerospike 8.0.0.17 backports the UDF and batch-write CVEs

    First-wave parity for the 8.0 branch, carrying the same three bulletin-backed fixes as 8.1.2.2. The pairing of a .17 and .18 release minutes apart shows the two waves were staged deliberately rather than merged.

    View source ↗
  5. 25d ago

    Aerospike 7.2.0.20 backports second-wave fixes to the 7.2 branch

    The 7.2 branch receives the msgpack out-of-bounds read, proxy memory leak and filter-expression validation fixes, plus a memory restriction change. Evidence that a branch two major versions back is still on the same security schedule as current.

    View source ↗
  6. 25d ago

    Aerospike 7.2.0.19 backports the UDF path traversal fix

    First-wave parity for 7.2, identical in security content to 7.1.0.25 published six minutes earlier and to 8.0.0.17 and 8.1.2.2 later the same day. The uniformity is the point: no branch waits for the next one.

    View source ↗