dbcve.org
Oaklouds OpenidApplication · Hgiga

CVE-2021-22851

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-19
Fix available
A fix is available. Upgrade to 2.0-54 / 3.0-54 or later.
See remediation →
100/100
Remediation priority · Urgent
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
HGiga EIP product contains SQL Injection vulnerability. Attackers can inject SQL commands into specific URL parameter (document management page) to obtain database schema and data.

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

SQL injection vulnerability in HGiga EIP product's document management page allows attackers to inject malicious SQL commands through URL parameters, potentially exposing the entire database schema and contents.

MitigationImplement parameterized queries/prepared statements for all database operations, apply strict input validation on all user-supplied parameters, and consider deploying a WAF with SQL injection rules as an additional layer of defense.

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
Oaklouds OpenidApplication
Affected:>= 2.0, < 2.0-54>= 3.0, < 3.0-54

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 if Hgiga Oaklouds Openid is installed
    Check your installed applications or software inventory for Hgiga Oaklouds Openid. Common locations include /opt/hgiga/, C:\Program Files\HGiga\, or consult your system administrator for installation paths.
    Affected if The software is present on the system
  2. Determine the installed version
    Locate version information in the product's about page, license file, or version metadata. Typical paths include the installation directory or the application's admin configuration panel. Compare the version number against the affected ranges: 2.0 through 2.0-53, or 3.0 through 3.0-53.
    Affected if The installed version falls within 2.0 <= version < 2.0-54 or 3.0 <= version < 3.0-54
  3. Verify the document management module is accessible
    Check if the document management functionality is enabled in the application. This is typically found in the admin control panel under module management or feature toggles. The vulnerable endpoint is typically accessed via the document management page URL.
    Affected if The document management module is enabled and accessible to users
  4. Inspect access logs for suspicious URL parameters
    Review web server or application logs for requests to the document management page containing unusual SQL-like characters such as quotes ('), semicolons (;), UNION SELECT, or common SQL injection patterns in URL parameters.
    Affected if SQL injection patterns are observed in logs for the document management endpoint

You are affected if Hgiga Oaklouds Openid version 2.0 through 2.0-53 or 3.0 through 3.0-53 is installed with the document management module enabled.

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 2.0-54 / 3.0-54 or later
Fixed in 2.0-543.0-54
Interim mitigation

Implement parameterized queries/prepared statements for all database operations, apply strict input validation on all user-supplied parameters, and consider deploying a WAF with SQL injection rules as an additional layer of defense.

Recommended fix Moderate confidence

Oaklouds OpenID version 2.0-54 or 3.0-54 (depending on your current major version)

  1. Upgrade Oaklouds OpenID version 2.0 to version 2.0-54 or later
  2. Upgrade Oaklouds OpenID version 3.0 to version 3.0-54 or later
  3. After upgrading, verify the fix by testing the document management page URL parameter to ensure SQL injection is no longer possible
  4. Confirm with vendor documentation or security advisories that these specific versions contain the SQL injection fix
Caveat Review vendor release notes for version 2.0-54 or 3.0-54 to check for any compatibility or configuration changes

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

Fix this in Oaklouds Openid Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,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 $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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