High [CVE-2025-61560] Rate limit bypass via race condition in SessionManager
This high-severity Red Hat Linux advisory covers CVE-2025-61560; related products: Red Hat Openshift Data Foundation 4, Red Hat OpenShift GitOps.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
Rate limit bypass via race condition in SessionManager. Red Hat rates this important (CVSS 8.1).
Weakness: CWE-307.
Affected products named by the advisory: Red Hat Openshift Data Foundation 4; Red Hat OpenShift GitOps.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Mitigation checklist
- To reduce exposure to brute-force attempts against authentication endpoints: 1. Rely on an external identity provider (such as Red Hat OpenShift OAuth or an enterprise SSO/OIDC provider) and disable the built-in local admin account by setting `admin.enabled: "false"` within the `argocd-cm` ConfigMap. 2. Restrict network access to the Argo CD API and web console to trusted internal networks using NetworkPolicies or firewall rules. 3. Enforce connection rate limiting at an upstream reverse proxy or ingress layer. Caveat: Disabling local accounts requires an operational external identity provider; ensure SSO is functional prior to disabling local authentication to avoid administrative lockout. Modifying the `argocd-cm` ConfigMap or ingress routing configuration may trigger a pod restart or reload of Argo CD server components.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.