ChainlinkLINK, coin
DevelopingProtocol update

Neo SPCC ships NeoFS REST Gateway v0.20.0 and Panel v0.11.1

Crypto News reports Neo SPCC released NeoFS REST Gateway v0.20.0 and NeoFS Panel v0.11.1, fixing a v2 session token clock skew issue and a prototype pollution flaw in Panel.

Why it matters

This is a routine software maintenance release for NeoFS storage software, with no market, regulatory or company-level consequences reported. The prototype pollution fix is the only item with a security dimension, and no exploitation of it was reported.

Key facts

Neo SPCC released NeoFS REST Gateway v0.20.0 and NeoFS Panel v0.11.1.

Reported by Crypto News (CryptoNews.net)

REST Gateway v0.20.0 fixes a clock skew issue that made newly issued v2 session tokens get rejected when the validating node's clock drifted from the issuer's.

Reported by Crypto News (CryptoNews.net)

The release fixes a parsing bug that returned empty rules instead of handling GETRANGEHASH records in container EACL, an issue first mitigated in v0.19.1 by skipping unsupported operations.

Reported by Crypto News (CryptoNews.net)

Object uploads with non-numeric __NEOFS__EXPIRATION_EPOCH attributes are now rejected with an HTTP 400 status.

400Reported by Crypto News (CryptoNews.net)

RANGE EACL operation support was removed from REST Gateway entirely.

Reported by Crypto News (CryptoNews.net)

The NeoFS SDK Go dependency was upgraded from RC22 to RC23, along with kin-openapi, viper and grpc.

Reported by Crypto News (CryptoNews.net)

Panel v0.11.1 adds compatibility with S3 Gateway 0.47.0 and the updated authboxsrv credential service, and restricts object previews to safe content types.

Reported by Crypto News (CryptoNews.net)

Panel v0.11.1 fixes a prototype pollution vulnerability when building the object tree and hardens handling of failed metadata fetches and network error states.

Reported by Crypto News (CryptoNews.net)

What happened

Crypto News reported that Neo SPCC released NeoFS REST Gateway v0.20.0, which fixes a clock skew problem that caused freshly issued v2 session tokens to be rejected when the validating node's clock drifted from the issuer's. The same release corrects a parsing bug that returned empty rules instead of handling GETRANGEHASH records in container EACL, a defect first worked around in v0.19.1 by skipping unsupported operations. According to the outlet, REST Gateway v0.20.0 also rejects uploads carrying non-numeric __NEOFS__EXPIRATION_EPOCH attributes with an HTTP 400 response, removes RANGE EACL operation support entirely, and upgrades the NeoFS Go SDK dependency from RC22 to RC23 along with kin-openapi, viper and grpc. In the companion Panel v0.11.1 release, served at panel.fs.neo.org, Crypto News said compatibility with S3 Gateway 0.47.0 and the authboxsrv credential service was added, object previews were restricted to safe content types, and a prototype pollution vulnerability in the object tree build was fixed, alongside hardened handling of failed metadata fetches and network errors and wallet fixes including acceptance of fractional GAS amounts for withdrawal. Only one outlet covered this, so the version numbers, the bug list and the dependency upgrades rest on that single report, and Neo SPCC published no separate statement in the evidence available here.

How the story developed

  1. First report

    First report by Crypto News (CryptoNews.net)

    Neo SPCC releases NeoFS REST Gateway v0.20.0, Panel v0.11.1

    Crypto News (CryptoNews.net)

  2. Update

    Neo SPCC releases NeoFS REST Gateway v0.20.0 and NeoFS Panel v0.11.1

    Single-source report covering clock skew fix for v2 session tokens, GETRANGEHASH EACL parsing fix, HTTP 400 rejection of non-numeric expiration attributes, RANGE EACL removal, SDK Go RC23 upgrade, Panel compatibility with S3 Gateway 0.47.0 and a prototype pollution fix.

    Crypto News (CryptoNews.net)

Affected entities

Original sources

PublisherReportRolePublished
Crypto News (CryptoNews.net)
Aggregator
Neo SPCC releases NeoFS REST Gateway v0.20.0, Panel v0.11.1Original