Template Service Broker OperatorApplication · Redhat
CVE-2020-1705
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 · uneditedA vulnerability was found in openshift/template-service-broker-operator in all 4.x.x versions prior to 4.3.0, where an insecure modification vulnerability in the /etc/passwd file was found in the openshift/template-service-broker-operator. An attacker with access to the container could use this flaw to modify /etc/passwd and escalate their privileges.
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 confidenceThe openshift/template-service-broker-operator in versions 4.x.x prior to 4.3.0 contains a container vulnerability allowing insecure modification of the /etc/passwd file. An attacker with container access can exploit this to modify user accounts and escalate privileges to root.
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
Template Service Broker OperatorApplication
>= 4.0.0, < 4.3.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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the template-service-broker-operator deploymentRun 'oc get deployment -n openshift-template-service-broker' to find the operator deployment in your clusterAffected if No deployment found means the operator is not installed and you are not affected
-
Retrieve the installed operator versionRun 'oc get clusteroperator template-service-broker -o jsonpath='{.status.versions[?(@.name=="operator")].version}'' or check the operator container image tagAffected if Version is 4.0.0 through 4.2.x (any version >= 4.0.0 and < 4.3.0) indicates you are running a vulnerable version
-
Confirm the exact operator version from the CSVRun 'oc get csv -n openshift-template-service-broker -o jsonpath='{.items[].spec.version}'' to get the ClusterServiceVersion versionAffected if Version falls within 4.0.0 to less than 4.3.0 confirms the vulnerability is present
-
Verify container write access to /etc/passwdCheck the operator pod security context: 'oc get pod -n openshift-template-service-broker -o jsonpath='{.items[*].spec.containers[*].securityContext}' and inspect if the container runs as privileged or has writable hostPath mountsAffected if Container runs as privileged or has writable /etc/passwd access indicates the exploit condition exists
You are affected if the template-service-broker-operator is deployed and its version is 4.0.0 or higher but lower than 4.3.0, and the container security allows modification of /etc/passwd
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.
From vendor data4.3.0
Upgrade the template-service-broker-operator to version 4.3.0 or later. Additionally, restrict container access and implement pod security policies to limit the attack surface.
Fix this in Template Service Broker Operator
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1705 — 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-2020-1705 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