dbcve.org
Open OndemandApplication · Osc

CVE-2020-36247

HIGH · 8.8 CVSS v3.1 Published 2021-02-19
Fix available
A fix is available. Upgrade to 1.5.7 / 1.6.22 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Open OnDemand before 1.5.7 and 1.6.x before 1.6.22 allows CSRF.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in Open OnDemand versions before 1.5.7 and 1.6.22 allows remote attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.

MitigationUpgrade to Open OnDemand version 1.5.7 or 1.6.22 or later, which include proper CSRF token validation for state-changing requests.

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
Open OndemandApplication
Affected:< 1.5.7>= 1.6.0, < 1.6.22

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 checks

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

  1. Identify Open OnDemand installation
    Check for Open OnDemand by looking for its installation directory (typically at /opt/ood or /var/www/ood), or by querying the system package manager (rpm -qa | grep ondemand or dpkg -l | grep ondemand)
    Affected if Open OnDemand is installed on the system
  2. Determine installed version
    Run the version command provided by Open OnDemand (ood version) or check the version file in the installation directory (cat /opt/ood/VERSION or similar), or query the RPM package database (rpm -q ondemand)
    Affected if The installed version cannot be determined or is lower than the safe versions
  3. Compare version against vulnerable ranges
    Review the installed version number against the affected ranges: versions below 1.5.7 and versions 1.6.0 through 1.6.21 are vulnerable
    Affected if Installed version is < 1.5.7 OR (installed version >= 1.6.0 AND installed version < 1.6.22)
  4. Confirm web service is running
    Check if the Open OnDemand web service is active by querying the service manager (systemctl status httpd-ood or similar) or by accessing the web interface
    Affected if The vulnerable version is installed AND the web service is active and accessible to users

A user is affected if Open OnDemand version 1.5.7 or later, or 1.6.22 or later, is NOT installed and the web service is running.

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.

From vendor data
Upgrade available Upgrade to 1.5.7 / 1.6.22 or later
Fixed in 1.5.71.6.22
Interim mitigation

Upgrade to Open OnDemand version 1.5.7 or 1.6.22 or later, which include proper CSRF token validation for state-changing requests.

Fix this in Open Ondemand Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-36247 — 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-2020-36247 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