GHSA-227r-jm2g-7cp4
MEDIUMSteeltoe's sensitive actuators (heapdump/env) only require Restricted permission
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Steeltoe.Management.Endpoint.NETSteeltoe.Management.EndpointBaseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Summary
All Steeltoe actuator endpoints default to EndpointPermissions.Restricted, which is mapped to Cloud Foundry's read_basic_data permission (granted to Space Auditors and similar low-trust roles). Sensitive actuators including heap dump, environment, and thread dump do not raise this to EndpointPermissions.Full, so CF's read_sensitive_data permission flag is not enforced for those endpoints. Spring Boot's equivalent Cloud Foundry integration gates these endpoints with read_sensitive_data by default.
Impact
Any CF user holding Space Auditor, Space Manager, or Org Auditor role can access the heap dump, environment, and thread dump actuators for any Steeltoe application in their space. A heap dump contains all in-memory data including database passwords, bearer tokens, and VCAP_SERVICES credentials. CF's read_sensitive_data permission, which is specifically designed to gate this access, has no effect.
Affected configuration
- Application is deployed on Cloud Foundry with CF actuator and security middleware active (added automatically by
AddAllActuators()when a CF environment is detected). - The attacker holds a CF role that grants
read_basic_data: Space Auditor, Space Manager, or Org Auditor.
Mitigations
If an immediate upgrade is not possible:
- Explicitly set
RequiredPermissions = EndpointPermissions.Fullin the options forHeapDumpEndpointOptions,EnvironmentEndpointOptions, andThreadDumpEndpointOptions. - If heap dump, thread dump, or environment are not needed in production, register only the required actuators individually instead of using
AddAllActuators().
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Steeltoe.Management.Endpoint | all versions | 4.2.0 |
| .NETNuGet | Steeltoe.Management.EndpointBase | all versions | 3.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Steeltoe.Management.Endpoint. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Steeltoe.Management.Endpoint to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-227r-jm2g-7cp4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-227r-jm2g-7cp4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-227r-jm2g-7cp4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-227r-jm2g-7cp4 in your dependencies?
O3 detects GHSA-227r-jm2g-7cp4 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.