### Summary `DataCenterInfo.FromJson` throws `ArgumentException` for any `name` value other than `"MyOwn"` or `"Amazon"`, despite the Java Eureka specification defining a third valid value: `"Netflix"`. The exception propagates through the entire registry deserialization chain and is swallowed by the periodic cache refresh task, leaving the local service registry permanently empty or stale. ### Impact Any registration with an unrecognized `DataCenterInfo.name` permanently disables service discovery for every Steeltoe Eureka client connected to the same registry. New clients start with an empty registry and running clients stop refreshing. The outage persists until the triggering registration is removed. Because `"Netflix"` is valid in the Java Eureka specification, a Java or Spring service in the same mesh can trigger this unintentionally. ### Affected configuration - Application uses the Steeltoe Eureka client (`EurekaDiscoveryClient`). - The registry contains at least one registration with a `DataCenterInfo.name` value other than `"MyOwn"` or `"Amazon"`. ### Mitigations If an immediate upgrade is not possible, remove any registrations using unsupported `DataCenterInfo.name` values from the registry. In mixed Java/Spring and Steeltoe environments, audit for the `Netflix` data center type before deploying Steeltoe Eureka clients.
### Summary `DataCenterInfo.FromJson` throws `ArgumentException` for any `name` value other than `"MyOwn"` or `"Amazon"`, despite the Java Eureka specification defining a third valid value: `"Netflix"`. The exception propagates through the entire registry deserialization chain and is swallowed by the periodic cache refresh task, leaving the local service registry permanently empty or stale. ### Impact Any registration with an unrecognized `DataCenterInfo.name` permanently disables service discovery for every Steeltoe Eureka client connected to the same registry. New clients start with an empty registry and running clients stop refreshing. The outage persists until the triggering registration is removed. Because `"Netflix"` is valid in the Java Eureka specification, a Java or Spring service in the same mesh can trigger this unintentionally. ### Affected configuration - Application uses the Steeltoe Eureka client (`EurekaDiscoveryClient`). - The registry contains at least one registration with a `DataCenterInfo.name` value other than `"MyOwn"` or `"Amazon"`. ### Mitigations If an immediate upgrade is not possible, remove any registrations using unsupported `DataCenterInfo.name` values from the registry. In mixed Java/Spring and Steeltoe environments, audit for the `Netflix` data center type before deploying Steeltoe Eureka clients.
### Summary `DataCenterInfo.FromJson` throws `ArgumentException` for any `name` value other than `"MyOwn"` or `"Amazon"`, despite the Java Eureka specification defining a third valid value: `"Netflix"`. The exception propagates through the entire registry deserialization chain and is swallowed by the periodic cache refresh task, leaving the local service registry permanently empty or stale. ### Impact Any registration with an unrecognized `DataCenterInfo.name` permanently disables service discovery for every Steeltoe Eureka client connected to the same registry. New clients start with an empty registry and running clients stop refreshing. The outage persists until the triggering registration is removed. Because `"Netflix"` is valid in the Java Eureka specification, a Java or Spring service in the same mesh can trigger this unintentionally. ### Affected configuration - Application uses the Steeltoe Eureka client (`EurekaDiscoveryClient`). - The registry contains at least one registration with a `DataCenterInfo.name` value other than `"MyOwn"` or `"Amazon"`. ### Mitigations If an immediate upgrade is not possible, remove any registrations using unsupported `DataCenterInfo.name` values from the registry. In mixed Java/Spring and Steeltoe environments, audit for the `Netflix` data center type before deploying Steeltoe Eureka clients.
### Summary `DataCenterInfo.FromJson` throws `ArgumentException` for any `name` value other than `"MyOwn"` or `"Amazon"`, despite the Java Eureka specification defining a third valid value: `"Netflix"`. The exception propagates through the entire registry deserialization chain and is swallowed by the periodic cache refresh task, leaving the local service registry permanently empty or stale. ### Impact Any registration with an unrecognized `DataCenterInfo.name` permanently disables service discovery for every Steeltoe Eureka client connected to the same registry. New clients start with an empty registry and running clients stop refreshing. The outage persists until the triggering registration is removed. Because `"Netflix"` is valid in the Java Eureka specification, a Java or Spring service in the same mesh can trigger this unintentionally. ### Affected configuration - Application uses the Steeltoe Eureka client (`EurekaDiscoveryClient`). - The registry contains at least one registration with a `DataCenterInfo.name` value other than `"MyOwn"` or `"Amazon"`. ### Mitigations If an immediate upgrade is not possible, remove any registrations using unsupported `DataCenterInfo.name` values from the registry. In mixed Java/Spring and Steeltoe environments, audit for the `Netflix` data center type before deploying Steeltoe Eureka clients.
Update Steeltoe.Discovery.Eureka to 4.2.0; Steeltoe.Discovery.Eureka to 3.4.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSteeltoe.Discovery.Eureka: Unrecognized DataCenterInfo.Name poisons entire registry fetch affects Steeltoe.Discovery.Eureka (nuget), Steeltoe.Discovery.Eureka (nuget). Severity is high. ### Summary `DataCenterInfo.FromJson` throws `ArgumentException` for any `name` value other than `"MyOwn"` or `"Amazon"`, despite the Java Eureka specification defining a third valid value: `"Netflix"`. The exception propagates through the entire registry deserialization chain and is swallowed by the periodic cache refresh task, leaving the local service registry permanently empty or stale. ### Impact Any registration with an unrecognized `DataCenterInfo.name` permanently disables service discovery for every Steeltoe Eureka client connected to the same registry. New clients start with an empty registry and running clients stop refreshing. The outage persists until the triggering registration is removed. Because `"Netflix"` is valid in the Java Eureka specification, a Java or Spring service in the same mesh can trigger this unintentionally. ### Affected configuration - Application uses the Steeltoe Eureka client (`EurekaDiscoveryClient`). - The registry contains at least one registration with a `DataCenterInfo.name` value other than `"MyOwn"` or `"Amazon"`. ### Mitigations If an immediate upgrade is not possible, remove any registrations using unsupported `DataCenterInfo.name` values from the registry. In mixed Java/Spring and Steeltoe environments, audit for the `Netflix` data center type before deploying Steeltoe Eureka clients.
AI coding agents often install or upgrade packages automatically in nuget. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| Steeltoe.Discovery.Eurekanuget | >=4.0.0,<=4.1.0 | 4.2.0 |
| Steeltoe.Discovery.Eurekanuget | <=3.3.0 | 3.4.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate Steeltoe.Discovery.Eureka to 4.2.0; Steeltoe.Discovery.Eureka to 3.4.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSteeltoe.Discovery.Eureka: Unrecognized DataCenterInfo.Name poisons entire registry fetch affects Steeltoe.Discovery.Eureka (nuget), Steeltoe.Discovery.Eureka (nuget). Severity is high. ### Summary `DataCenterInfo.FromJson` throws `ArgumentException` for any `name` value other than `"MyOwn"` or `"Amazon"`, despite the Java Eureka specification defining a third valid value: `"Netflix"`. The exception propagates through the entire registry deserialization chain and is swallowed by the periodic cache refresh task, leaving the local service registry permanently empty or stale. ### Impact Any registration with an unrecognized `DataCenterInfo.name` permanently disables service discovery for every Steeltoe Eureka client connected to the same registry. New clients start with an empty registry and running clients stop refreshing. The outage persists until the triggering registration is removed. Because `"Netflix"` is valid in the Java Eureka specification, a Java or Spring service in the same mesh can trigger this unintentionally. ### Affected configuration - Application uses the Steeltoe Eureka client (`EurekaDiscoveryClient`). - The registry contains at least one registration with a `DataCenterInfo.name` value other than `"MyOwn"` or `"Amazon"`. ### Mitigations If an immediate upgrade is not possible, remove any registrations using unsupported `DataCenterInfo.name` values from the registry. In mixed Java/Spring and Steeltoe environments, audit for the `Netflix` data center type before deploying Steeltoe Eureka clients.
AI coding agents often install or upgrade packages automatically in nuget. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| Steeltoe.Discovery.Eurekanuget | >=4.0.0,<=4.1.0 | 4.2.0 |
| Steeltoe.Discovery.Eurekanuget | <=3.3.0 | 3.4.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard