Steeltoe.Management.Endpoint
Affected
- introduced
0, fixed4.2.0(ecosystem)
Fixed versions
4.2.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-50200
Steeltoe's env sanitizer misses connection strings — leaks embedded DB passwords
Summary
The Sanitizer component in the Environment actuator redacts configuration values by matching the configuration key name against a suffix list. The default list (password, secret, key, token, .*credentials.*, vcap_services) does not cover the standard .NET pattern ConnectionStrings:<name> or Steeltoe Connectors' Steeltoe:Client:<type>:Default:ConnectionString. There is no value-based scrubbing, so full connection string values including embedded Password= and user:pass@host segments are returned verbatim in /actuator/env responses.
Impact
Any caller who can reach /actuator/env can receive connection strings containing plaintext credentials. Those credentials enable direct connection to the backing database, bypassing the application tier.
Affected configuration
ConnectionStrings:* or *:ConnectionString keys.env is added to Management:Endpoints:Actuator:Exposure:Include. This is not the default./cloudfoundryapplication/env path is accessible to any authenticated CF user with read_basic_data permissions (Space Auditor and above) regardless of the exposure configuration.Mitigations
If an immediate upgrade is not possible:
env from the actuator exposure list..*connectionstring.* to KeysToSanitize as a defense-in-depth measure for both paths.High Basis: The source's own band: HIGH
0, fixed 4.2.0 (ecosystem)4.2.0
The export has no generic command for this ecosystem.
0, fixed 3.4.0 (ecosystem)3.4.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0