0x63d51f7663d5…63d51f73

ConfirmedSecurity721 vB58 sat/vB4 min decode

NeoFS Node patches authentication and storage integrity flaws

NeoFS Node v0.58.1 and v0.58.2 fix N3 witness authentication, session-token replay risks, replica retention flaws and $LINK validation defects across storage nodes.

NeoFS Node v0.58.1, v0.58.2 patch authentication vulnerabilities, harden storage integrity
WitnessNeoFS Node v0.58.1, v0.58.2 patch authentication vulnerabilities, harden storage integrityfrabre / pixabay

Outputs

  1. NeoFS Node v0.58.2 ships 17 storage and reliability fixes.

  2. PR #4271 corrected N3 witness verification for arbitrary account authentication.

  3. PR #4277 binds object-service session tokens to request signers.

  4. PR #4306 closes seven distinct $LINK object-validation issues.

  5. Both releases support three operating systems across amd64 and arm64 architectures.

nspcc-dev’s NeoFS Node v0.58.2 ships 17 fixes for storage redundancy, object validation and operational stability, following v0.58.1’s patches to N3 witness authentication and object-service session tokens, according to the project’s GitHub release notes.

PR #4271 fixes N3 witness verification in v0.58.1 because the verification script was not bound to the claimed account. Any script that unconditionally returned a truthy value could authenticate as any account, regardless of whether the script hash corresponded to that account.

PR #4277 binds object-service session tokens to the request signer, preventing potential token replay or cross-signer reuse. The release notes describe these as preventive risks and do not report exploitation, affected node counts or losses.

What changed in v0.58.1 beyond authentication?

  • PR #4258 and PR #4259 add N3 signature support for container and object operations.
  • The release corrects ranged GET streaming for split objects, invalidates the container cache after attribute changes, and resolves a panic triggered by container PUT requests with unsigned eACL tables.
  • It also enforces that notary events originate from the same contract.

The practical takeaway is that v0.58.1 closes specific authentication and container-operation gaps, although the release notes do not constitute a broader security audit.

How does v0.58.2 reduce data-loss risk?

PR #4291 changes the policer’s replica-retention logic to address a scenario in which the only verified local copy of an object could be dropped during transient peer failures or maintenance windows. The release notes provide no evidence of completed data loss, so operators should treat this as a preventive integrity control rather than a confirmed incident.

In plain terms, the patch is intended to keep a verified local copy available when neighboring nodes or maintenance activity temporarily disappear.

Which $LINK validation defects were closed?

PR #4306 closes seven distinct issues in $LINK object validation. The named examples include missing parent-presence checks, acceptance of invalid single-child $LINK objects, failure to verify that children’s sizes sum to the parent length, and a Get-service panic when processing malformed LINKs.

The release note identifies four examples within the seven-issue set rather than describing every defect. The practical effect is stricter parent validation and fewer malformed-link paths reaching the object service.

How are erasure coding and remote metadata hardened?

PR #4293 prevents an infinite restoration loop in the policer, while PR #4287 bounds buffer allocation when a container peer declares an oversized parent payload. PR #4290 verifies parent object headers collected from other nodes against the requested object ID before the node uses them.

Together, these changes tighten recovery behavior, constrain memory use and require stricter checks on metadata supplied by peers.

Which reliability failures were corrected?

PR #4282 prevents YAML parsing panics when struct-slice fields have an incorrect shape. PR #4286 corrects gRPC server misattribution after a SIGHUP reload, and PR #4292 resolves a SearchV2 crash caused by zero-attribute responses from container nodes.

Taken together, the fixes remove crash and reload failure modes from routine node operations, although the notes provide no failure-rate data or estimate of previous exposure.

How does the release handle expiration and split-object replication?

Three fixes address object-lifecycle controls. PR #4303 exposes object expiration time to eACL filters; PR #4276 prevents replication of expired split parts from incomplete uploads; and PR #4252 delays garbage collection of expired split-object parents to reduce resurrection risk from lagging replication.

The practical result is tighter policy input and less opportunity for expired, incompletely replicated objects to return after deletion.

Who should upgrade, and where?

The project recommends that node operators update, particularly in production deployments. Its guidance calls v0.58.1 critical for nodes serving ACL-protected containers, while v0.58.2 addresses data-integrity risks affecting erasure-coded and split objects.

Both releases support Linux, macOS and Windows on amd64 and arm64 architectures. The project provides the v0.58.1 release notes and v0.58.2 release notes.

The guidance specifies no migration deadline or sequencing between the two tags, so operators should verify which patches their deployed build contains. With no rollout date stated, the practical checkpoint is the next production maintenance cycle, when teams can confirm that the authentication and storage-integrity fixes are running across supported platforms.

via cryptonews.net (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,525 articles