Bug 2390860

Summary: toolbox: go-viper's mapstructure May Leak Sensitive Information in Logs [fedora-41]
Product: [Fedora] Fedora Reporter: Jon Moroney <jmoroney>
Component: toolboxAssignee: Debarshi Ray <debarshir>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 41CC: debarshir, go-sig, harrymichal, patrick, sumukher
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["2289ae97-0e23-4686-a41c-7ca147a1369f"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-08-27 23:38:46 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:    
Bug Blocks: 2390114    

Description Jon Moroney 2025-08-25 17:55:10 UTC 
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Comment 1 Debarshi Ray 2025-08-27 23:32:07 UTC 
This security issue doesn't impact Toolbx, even though the vulnerable code is present in Toolbx's dependency chain.

github.com/go-viper/mapstructure/v2 is an indirect dependency of Toolbx because of github.com/spf13/viper.  Toolbx uses Viper to read and parse its configuration files, which don't have any sensitive data.  Therefore, there's no sensitive data for mapstructure to leak in the logs.

The github.com/go-viper/mapstructure/v2 version has been updated in Toolbx upstream, merely to keep the dependencies updated, but there's no need to do a downstream build, because there's no security issue to be addressed.