dbcve.org
OpenctiApplication · Citeum

CVE-2022-30290

HIGH · 7.5 CVSS v3.1 Published 2022-07-05
Fix available
A fix is available. Upgrade to after 5.2.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
In OpenCTI through 5.2.4, a broken access control vulnerability has been identified in the profile endpoint. An attacker can abuse the identified vulnerability in order to arbitrarily change their registered e-mail address as well as their API key, even though such action is not possible through the interface, legitimately.

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 confidence

OpenCTI versions through 5.2.4 contain a broken access control vulnerability in the profile endpoint that allows authenticated users to modify their registered email address and API key through direct API manipulation, bypassing restrictions enforced in the web interface.

MitigationUpgrade to OpenCTI version 5.2.5 or later which addresses the broken access control in the profile endpoint.

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
OpenctiApplication
Affected:<= 5.2.4

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenCTI version
    Locate the OpenCTI version information in the application frontend, configuration files, or container metadata. Common locations include the About section in the web UI, Docker image tags, or version configuration files.
    Affected if The installed version is 5.2.4 or earlier (any version through 5.2.4)
  2. Confirm API endpoint accessibility
    Verify that the profile API endpoint is accessible to authenticated users by reviewing API routing configuration or testing with a low-privilege authenticated session.
    Affected if Authenticated users can access the profile API endpoint at /api/users/me or similar profile modification routes
  3. Test API vs web interface validation consistency
    Compare the validation enforced by the web interface for email and API key modifications against the validation enforced by the direct API endpoint. Submit a profile modification request via the API with values that the web interface would reject.
    Affected if The API endpoint accepts modifications (email address or API key changes) that the web interface blocks, indicating the API bypasses web interface restrictions
  4. Review API request parameters accepted
    Inspect the API request schema or endpoint code to determine if the profile update endpoint accepts email and api_key fields as writable parameters.
    Affected if The profile update API endpoint accepts and processes email or api_key parameter modifications

The environment is affected if running OpenCTI version 5.2.4 or earlier and the profile API endpoint allows authenticated users to modify their email address or API key in ways that the web interface restricts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.2.4
Interim mitigation

Upgrade to OpenCTI version 5.2.5 or later which addresses the broken access control in the profile endpoint.

Recommended fix Moderate confidence

OpenCTI 5.2.5 or later

  1. 1. Backup your current OpenCTI installation and database before proceeding with any upgrade.
  2. 2. Check the official OpenCTI GitHub repository (github.com) for the release notes of version 5.2.5 or later to confirm the security fix.
  3. 3. Follow the standard OpenCTI upgrade procedure documented in the official installation guide.
  4. 4. After upgrading, verify that the profile endpoint now properly enforces authorization checks.
  5. 5. Confirm that users can no longer arbitrarily modify their email address or API key through direct API calls that should be restricted.
Caveat Review release notes for any breaking changes between 5.2.4 and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opencti Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30290 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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