CVE-2024-25011
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 Catalog Manager and Ericsson Order Care APIs do not have authentication enabled by default. Authentication checks can be configured to remediate the information disclosure issue.
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 · moderate confidenceEricsson Catalog Manager and Ericsson Order Care APIs are shipped with authentication disabled by default, allowing unauthenticated remote attackers to access sensitive API endpoints and potentially retrieve confidential business or customer data through the exposed interfaces.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 installed Ericsson API productsSearch the system for Ericsson Catalog Manager or Ericsson Order Care installations. Check for installation directories, services, or applications with these names. Look in common installation paths or use system inventory tools.Affected if Either Ericsson Catalog Manager or Ericsson Order Care is installed on the system
-
Locate authentication configuration filesSearch for configuration files related to authentication settings in the Ericsson API installation directories. Look for files named auth.config, security.xml, application.properties, or similar that control API authentication.Affected if Authentication configuration files exist and show authentication is disabled or set to a permissive state
-
Check API endpoint accessibility without credentialsAttempt to access the Catalog Manager or Order Care API endpoints using HTTP/HTTPS requests without providing any authentication headers or credentials. For example, curl or browser requests to typical API paths like /api/catalog or /api/orders.Affected if The API returns valid data or successful responses without requiring any authentication
-
Verify authentication enforcement on endpointsReview the API configuration or deployment descriptors to confirm whether authentication enforcement is explicitly enabled. Check for settings like 'auth.required=true', security constraints, or authentication middleware.Affected if Authentication enforcement is not explicitly enabled or is set to disabled/default
The environment is affected if Ericsson Catalog Manager or Order Care APIs are present and authentication is either disabled by default or not explicitly configured, allowing unrestricted API access without credentials.
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 dataEnable and configure authentication mechanisms on the affected APIs, ensuring all endpoints require valid credentials before returning any data.
- 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-25011 — 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-25011 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