Openshift ServerlessApplication · Redhat
CVE-2021-3703
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 · uneditedIt was found that the CVE-2021-27918, CVE-2021-31525 and CVE-2021-33196 have been incorrectly mentioned as fixed in RHSA for Serverless 1.16.0 and Serverless client kn 1.16.0. These have been fixed with Serverless 1.17.0.
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 confidenceThis CVE documents a documentation/advisory error in Red Hat's security announcement (RHSA) for Serverless 1.16.0. The advisory incorrectly stated that CVE-2021-27918, CVE-2021-31525, and CVE-2021-33196 were fixed in version 1.16.0, when these vulnerabilities were actually only addressed in version 1.17.0. Users relying on the 1.16.0 advisory remained vulnerable to the three underlying CVEs.
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
Openshift ServerlessApplication
< 1.17.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify OpenShift Serverless installationRun 'oc get clusterserviceversion -n openshift-operators' or check the OperatorHub for installed Serverless OperatorAffected if OpenShift Serverless is not installed or cannot be determined
-
Determine Serverless Operator versionRun 'oc get clusterserviceversion serverless-operator.v -n openshift-operators -o jsonpath={.spec.version}' or check the installed version in OperatorHubAffected if Version is 1.16.0 or earlier (less than 1.17.0)
-
Verify Knative Serving versionRun 'oc get knativeserving serverless -n knative-serving -o jsonpath={.spec.version}' or check the KnativeServing CR statusAffected if Version corresponds to Serverless 1.16.0 or earlier
User is affected if Red Hat OpenShift Serverless is installed at a version below 1.17.0, as the advisory incorrectly claimed fixes for CVE-2021-27918, CVE-2021-31525, and CVE-2021-33196 that were only actually addressed in 1.17.0.
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.
dbcve · scoped1.17.0
Users of Serverless 1.16.0 and kn client 1.16.0 should upgrade to Serverless 1.17.0 or later to obtain the actual fixes for CVE-2021-27918, CVE-2021-31525, and CVE-2021-33196.
OpenShift Serverless 1.17.0 or later
- Upgrade OpenShift Serverless to version 1.17.0 or later to resolve the incorrectly documented CVE fixes (CVE-2021-27918, CVE-2021-31525, CVE-2021-33196)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Openshift Serverless
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3703 — 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-2021-3703 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