dbcve.org
Noobaa OperatorApplication · Redhat

CVE-2021-3529

HIGH · 7.1 CVSS v3.1 Published 2021-06-02
Fix available
A fix is available. Upgrade to 5.7.0 or later.
See remediation →
78/100
Remediation priority · High
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
A flaw was found in noobaa-core in versions before 5.7.0. This flaw results in the name of an arbitrarily URL being copied into an HTML document as plain text between tags, including potentially a payload script. The input was echoed unmodified in the application response, resulting in arbitrary JavaScript being injected into an application's response. The highest threat to the system is for confidentiality, availability, and integrity.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in noobaa-core versions before 5.7.0. The application copies user-supplied URL names into HTML documents without proper sanitization or output encoding, allowing arbitrary JavaScript to be injected into the application's response.

MitigationUpgrade to noobaa-core version 5.7.0 or later. Additionally, implement proper input validation and output encoding for all user-supplied data before rendering in HTML contexts.

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
Noobaa OperatorApplication
Affected:< 5.7.0
Openshift Container PlatformApplication
Affected:= 4.0

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 the installed Noobaa Operator version
    Run 'noobaa version' or check the operator deployment image tag in your OpenShift cluster. You can also query the operator CSV: 'oc get csv -n openshift-storage'
    Affected if The version displayed is before 5.7.0 (any version < 5.7.0 is affected)
  2. Check the noobaa-core image version
    Inspect the noobaa-core pod container image: 'oc get pods -n openshift-storage -o jsonpath={.items[*].spec.containers[*].image}'
    Affected if The image version/tag indicates a build before version 5.7.0
  3. Verify if user-supplied URLs are accepted
    Check if your Noobaa deployment allows users to create or modify bucket endpoints, S3 connections, or any feature where URL names can be supplied. Review custom resources: 'oc get noobaa -A' and inspect any backingstore or bucketclass definitions
    Affected if Users have the ability to provide custom URL names or endpoint configurations that get rendered in the UI or API responses
  4. Inspect for existing injected scripts
    Review browser developer console console logs and network traffic for any XSS warnings. Check any web application logs for patterns like '<script' or 'javascript:' in URL-related fields
    Affected if Unexpected script tags or javascript: protocols appear in URL-related fields or are logged as errors

You are affected if your Noobaa Operator or noobaa-core version is any build earlier than 5.7.0 and your deployment accepts user-supplied URL names in bucket, endpoint, or backingstore configurations.

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 5.7.0 or later
Fixed in 5.7.0
Interim mitigation

Upgrade to noobaa-core version 5.7.0 or later. Additionally, implement proper input validation and output encoding for all user-supplied data before rendering in HTML contexts.

Fix this in Noobaa Operator 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-2021-3529 — 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-3529 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