Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') The advisory has been revoked - it doesn't affect any version of package nextcloud-server-32  (opens in a new tab)

The Wolfi security team deemed this advisory irrelevant for Wolfi:latest.

Note: Versions mentioned in the description apply only to the upstream nextcloud-server-32 package and not the nextcloud-server-32 package as distributed by Wolfi.

axios versions >=1.15.2 and <1.18.0 contain prototype-pollution read-side gadgets in Basic auth subfield handling (lib/adapters/http.js and lib/helpers/resolveConfig.js). When an application is already affected by a separate prototype-pollution primitive and makes an axios request with an own auth object that omits the username and/or password properties, axios reads the inherited Object.prototype.username and Object.prototype.password values and uses them to construct an outbound 'Authorization: Basic ...' header. axios itself does not pollute prototypes. The practical impact is outbound request tampering: an attacker who controls the polluted prototype values can inject attacker-chosen Basic auth credentials or replace an existing Authorization header. Credential disclosure is only possible under additional application-specific conditions.

• https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-auth-subfields
• https://github.com/axios/axios/security/advisories/GHSA-xj6q-8x83-jv6g