CVE-2024-25008
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEricsson RAN Compute and Site Controller 6610 contains a vulnerability in the Control System where Improper Input Validation can lead to arbitrary code execution, for example to obtain a Linux Shell with the same privileges as the attacker. The attacker would require elevated privileges for example a valid OAM user having the system administrator role to exploit the vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper Input Validation vulnerability in the Control System of Ericsson RAN Compute and Site Controller 6610 allows an authenticated attacker with OAM system administrator privileges to achieve arbitrary code execution, potentially obtaining a Linux shell with elevated privileges. The vulnerability stems from insufficient validation of user input within the Control System component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the product and versionLocate the installed version of Ericsson RAN Compute and Site Controller 6610. This is typically found in the system management interface, build documentation, or via CLI command 'version' or 'show system info' if available.Affected if The installed version falls within the vulnerable version range for this model.
-
Verify Control System component statusCheck whether the Control System component is enabled and accessible in the deployment. This may be visible in the system configuration, service status, or management interface under component listings.Affected if The Control System component is enabled and exposed to OAM access.
-
Review OAM administrator account configurationExamine the OAM (Operations and Maintenance) system for accounts with system administrator privileges. Use the user management or access control panel to list privileged accounts.Affected if An OAM account with system administrator privileges exists and is active.
-
Confirm OAM interface accessibilityVerify that the OAM management interface is network-accessible. Check firewall rules, ACLs, or network segmentation settings that control access to the OAM portal or CLI.Affected if The OAM interface is accessible from a network segment where an attacker could authenticate.
A user is affected if they run a vulnerable version of Ericsson RAN Compute and Site Controller 6610 with the Control System enabled and have OAM system administrator accounts accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-provided patch from Ericsson to address the improper input validation in the Control System. Verify that OAM access controls and privilege assignments follow least-privilege principles until the patch is deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data