CVE-2024-11071
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 · uneditedPermissive Cross-domain Policy with Untrusted Domains vulnerability in local API server of DestinyECM solution(versions described below) which is developed and maintained by Cyberdigm may allow Cross-Site Request Forgery (CSRF) attack, which probabilistically enables JSON Hijacking (aka JavaScript Hijacking) via forgery web page.* Due to product customization, version information may differ from the following version description. For further inquiries, please contact the vendor.
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 confidencePermissive cross-domain policy vulnerability in DestinyECM local API server allows untrusted external domains to make requests to the API, enabling Cross-Site Request Forgery (CSRF) attacks and probabilistic JSON hijacking through malicious forged web pages.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate DestinyECM API server configuration filesSearch for configuration files in the DestinyECM installation directory, typically named cors.config, api.config, server.config, or similar, and check for CORS-related settings such as 'allow-origin', 'cors', or 'cross-domain' entries.Affected if Configuration contains wildcard '*' or allows untrusted/origin domains in CORS settings
-
Inspect API HTTP responses for CORS headersSend a request to the ECM API endpoints (e.g., using curl -H 'Origin: http://malicious-site.com' -I <api-url>) and examine response headers for Access-Control-Allow-Origin header.Affected if The Access-Control-Allow-Origin header returns '*' or echoes back the untrusted Origin value without validation
-
Verify Origin header validation in server codeReview the DestinyECM server-side code or configuration for Origin header validation logic - check if the server validates allowed origins against a whitelist before responding.Affected if No server-side validation of the Origin header exists or all origins are accepted by default
-
Check API cookie configuration for SameSite attributeInspect the API's session cookie settings by logging in and examining cookie headers (curl -v <login-url>) for the SameSite attribute and Secure flag.Affected if Cookies lack SameSite attribute or use SameSite=None without Secure flag, making them vulnerable to CSRF
-
Identify exposed API endpointsDocument all accessible API endpoints served by the DestinyECM local server and test each for CORS header presence.Affected if Any endpoint returns permissive CORS headers allowing cross-origin access from untrusted domains
Your environment is affected if the DestinyECM API server returns permissive CORS headers (wildcard '*' or unvalidated Origin) or lacks proper Origin header validation, enabling attacker-controlled pages to make authenticated requests on behalf of users.
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 dataRestrict cross-domain policy or CORS headers to only allow trusted domains, and implement CSRF tokens or SameSite cookie attributes to prevent forged requests.
- 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-11071 — 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-11071 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