When enabling trace logging in Spring Cloud Config Server sensitive information was placed in plain text in the logs
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.1.14, 4.1.10, 4.2.7 and 2 more.
When enabling trace logging in Spring Cloud Config Server sensitive information was placed in plain text in the logs. Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater. Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | >=3.1.0 <3.1.14, >=4.1.0 <4.1.10, >=4.2.0 <4.2.7, >=4.3.0 <4.3.3, >=5.0.0 <5.0.3 | 3.1.14, 4.1.10, 4.2.7, 4.3.3, 5.0.3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket