CVE-2024-25007
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 Network Manager (ENM), versions prior to 23.1, contains a vulnerability in the export function of application log where Improper Neutralization of Formula Elements in a CSV File can lead to code execution or information disclosure. There is limited impact to integrity and availability. The attacker on the adjacent network with administration access can 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 confidenceEricsson Network Manager (ENM) versions prior to 23.1 contain a CSV injection vulnerability in the application log export function. Improper neutralization of formula elements in the exported CSV file allows an attacker with adjacent network access and administration privileges to potentially execute arbitrary code or disclose sensitive information through malicious spreadsheet formulas.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:L
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 installed ENM versionUse the ENM administrative interface or system inventory tools to determine the currently running Ericsson Network Manager version numberAffected if The installed version is any release prior to 23.1 (for example, 22.x, 21.x, or earlier releases)
-
Confirm log export function is accessibleVerify that the application log export feature is enabled and available in the ENM web interface or CLIAffected if The log export functionality is present and accessible to administrative users
-
Verify administrative access existsCheck whether the account being used or any administrative accounts in the system have privileges to access the log export featureAffected if Administrative credentials or privileges are configured for the ENM system
-
Assess network exposureDetermine if the ENM management interface is reachable from adjacent network segmentsAffected if The ENM application is accessible from network segments beyond the local management network (adjacent network access is possible)
-
Review recent log export activityExamine ENM audit logs or access logs for any log export operations, checking for suspicious patterns or unexpected CSV file generationAffected if Log export activity shows unexpected or unauthorized CSV file generation that may indicate exploitation attempts
A user is affected if the ENM version is below 23.1 and the log export function is accessible to an attacker with adjacent network access and administrative privileges.
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.
dbcve · scoped23.1
Upgrade Ericsson Network Manager to version 23.1 or later to receive the vendor patch that addresses the CSV formula injection vulnerability.
Ericsson Network Manager 23.1
- Contact Ericsson support or access the Ericsson official portal to obtain the Network Manager 23.1 upgrade package
- Review upgrade documentation and pre-upgrade requirements specific to your ENM deployment
- Schedule a maintenance window considering the upgrade impact
- Backup current ENM configuration and data
- Execute the upgrade following Ericsson's documented upgrade procedure for Network Manager
- Verify the upgrade was successful and the export function operates correctly
- Confirm the version shows 23.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,792.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25007 — 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-25007 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