Bug 2074689 (CVE-2022-21803)

Summary:	CVE-2022-21803 nconf: Prototype pollution in memory store
Product:	[Other] Security Response	Reporter:	Pedro Sampaio <psampaio>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	fjansen, gparvin, jramanat, njean, pahickey, stcannon
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	npm-nconf 0.11.4	Doc Type:	If docs needed, set a value
Doc Text:	A flaw was found in the nconf library when setting the configuration properties. This flaw allows an attacker to provide a crafted property, leading to prototype object pollution.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-05 09:46:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2075099, 2075100, 2075101, 2075102, 2075103, 2075104, 2075105, 2076838, 2076841, 2077929, 2077930, 2078021, 2085279
Bug Blocks:	2074691

Description Pedro Sampaio 2022-04-12 19:37:44 UTC

This affects the package nconf before 0.11.4. When using the memory engine, it is possible to store a nested JSON representation of the configuration. The .set() function, that is responsible for setting the configuration properties, is vulnerable to Prototype Pollution. By providing a crafted property, it is possible to modify the properties on the Object.prototype. Ps.: The fixed version is not fixed completely in 0.11.4 as it stills affects org.webjars.npm:nconf.

References:

https://snyk.io/vuln/SNYK-JS-NCONF-2395478
https://github.com/indexzero/nconf/releases/tag/v0.11.4
https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2632450
https://github.com/indexzero/nconf/pull/397

Comment 2 juneau 2022-04-13 16:54:14 UTC

services-insights-essentials/remediations/insights-remediations:f169564/nconf-0.10.0 https://github.com/RedHatInsights/insights-remediations/blob/master/package-lock.json
services-insights-essentials/remediations/remediations:f169564/nconf-0.10.0 https://github.com/RedHatInsights/insights-remediations/blob/production/package-lock.json

Comment 4 errata-xmlrpc 2022-05-03 16:43:55 UTC

This issue has been addressed in the following products:

  Red Hat Advanced Cluster Management for Kubernetes 2.4 for RHEL 8

Via RHSA-2022:1681 https://access.redhat.com/errata/RHSA-2022:1681

Comment 5 errata-xmlrpc 2022-05-05 02:39:13 UTC

This issue has been addressed in the following products:

  Red Hat Advanced Cluster Management for Kubernetes 2.3 for RHEL 7
  Red Hat Advanced Cluster Management for Kubernetes 2.3 for RHEL 8

Via RHSA-2022:1715 https://access.redhat.com/errata/RHSA-2022:1715

Comment 6 Product Security DevOps Team 2022-05-05 09:46:22 UTC

This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-21803

Comment 7 errata-xmlrpc 2022-06-09 02:06:54 UTC

This issue has been addressed in the following products:

  Red Hat Advanced Cluster Management for Kubernetes 2.5 for RHEL 8

Via RHSA-2022:4956 https://access.redhat.com/errata/RHSA-2022:4956

Comment 8 errata-xmlrpc 2022-06-27 17:03:45 UTC

This issue has been addressed in the following products:

  Red Hat Advanced Cluster Management for Kubernetes 2.4 for RHEL 8

Via RHSA-2022:5201 https://access.redhat.com/errata/RHSA-2022:5201

Comment 9 errata-xmlrpc 2022-06-28 17:06:15 UTC

This issue has been addressed in the following products:

  Red Hat Advanced Cluster Management for Kubernetes 2.3 for RHEL 8
  Red Hat Advanced Cluster Management for Kubernetes 2.3 for RHEL 7

Via RHSA-2022:5392 https://access.redhat.com/errata/RHSA-2022:5392