CWE-269
DiscouragedImproper Privilege Management
Abstraction: Class · Status: Draft
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
6590 vulnerabilities reference this CWE, most recent first.
GHSA-QF5P-C774-J224
Vulnerability from github – Published: 2022-05-24 17:18 – Updated: 2026-08-19 18:31An elevation of privilege vulnerability exists when the Windows Common Log File System (CLFS) driver improperly handles objects in memory, aka 'Windows Common Log File System Driver Elevation of Privilege Vulnerability'.
{
"affected": [],
"aliases": [
"CVE-2020-1154"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-05-21T23:15:00Z",
"severity": "HIGH"
},
"details": "An elevation of privilege vulnerability exists when the Windows Common Log File System (CLFS) driver improperly handles objects in memory, aka \u0027Windows Common Log File System Driver Elevation of Privilege Vulnerability\u0027.",
"id": "GHSA-qf5p-c774-j224",
"modified": "2026-08-19T18:31:24Z",
"published": "2022-05-24T17:18:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-1154"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-1154"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1154"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QF5V-M7P4-95RP
Vulnerability from github – Published: 2026-07-28 20:12 – Updated: 2026-07-28 20:12Fission v1.24.0 added PodSpec safety validation for tenant-facing Environment and Function CRDs (ValidatePodSpecSafety / ValidateContainerSafety admission webhook + sanitizeContainerSecurityContext executor merge layer), but the
capability check was implemented as a fixed denylist of six Linux capabilities (SYS_ADMIN, NET_ADMIN, SYS_PTRACE, SYS_MODULE, DAC_READ_SEARCH, DAC_OVERRIDE). The denylist omitted CAP_SYS_TIME, among others. As a result, a tenant
who could create a Function or Environment CRD could request securityContext.capabilities.add: ["SYS_TIME"], pass Fission's admission validation and merge-layer sanitization, and run attacker-controlled code with CAP_SYS_TIME in the
resulting function or runtime container.
Demonstrated consequence: cross-tenant node integrity damage via CAP_SYS_TIME. The Linux real-time clock is not namespaced — time namespaces virtualize only MONOTONIC and BOOTTIME, never REALTIME — so a tenant container holding
CAP_SYS_TIME could call clock_settime(CLOCK_REALTIME) and rewrite the shared node wall clock. That corrupts TLS / certificate validity windows, Kubernetes lease renewal, token expiry, scheduling, and time-series for every workload on
the node.
The denylist also omitted SYS_RAWIO, BPF, SYS_RESOURCE, and MAC_ADMIN. Those are documented as evidence that the denylist is structurally incomplete (their practical impact is kernel-, LSM-, or device-cgroup-dependent and is not
exercised in this report).
The deeper structural problem: a denylist on capabilities.add cannot constrain capabilities the OCI runtime grants by default — DAC_OVERRIDE is in the OCI default cap set and reaches the container regardless of any add check,
partially mooting the denylist for its own entries. A capability allowlist (with drop:["ALL"] to remove the default set) is the only model that addresses both problems.
Affected
- Project:
github.com/fission/fission - Versions:
<= 1.24.0 - Audited commits: v1.24.0 tag (
ce617120) and current HEAD at audit time - Component:
pkg/apis/core/v1/podspec_safety.go(dangerousCapabilities) andpkg/executor/util/merge.go(dangerousMergeContainerCapabilities) - Pre-condition: cluster does not enforce a restrictive Pod Security Admission (PSA) profile on the function-pod namespace. With PSA
restrictedin force the API server's PodSecurity admission rejects the pod at creation and this finding does not apply. Fission added its own PodSpec validation precisely because it cannot assume PSA enforcement.
Fix section (paste into the Fix / Patches field)
Fixed in v1.25.0 by:
- PR #3465 (commit
2569b42b) — replace the denylist with a PSA-restricted allowlist (NET_BIND_SERVICEonly) at both enforcement layers: pkg/apis/core/v1/podspec_safety.go—ValidateContainerSafetynow rejects anycapabilities.addentry not inallowedCapabilities. The container check is invoked fromValidatePodSpecSafetyfor every PodSpec container / init-container and fromEnvironment.validateForAdmissionfor the bareRuntime.Container/Builder.Container.pkg/executor/util/merge.go—sanitizeContainerSecurityContextfilterscapabilities.addthrough the same allowlist at every merge site (poolmgr / newdeploy / container executor / builder).- The same PR adds 21 bounded CEL
XValidationrules covering the cheap pod-level invariants (hostNetwork/hostPID/hostIPC/serviceAccountName/serviceAccountoverride) onFunctionSpec,Runtime, andBuilder, plus the bare-ContainerSecurityContextchecks (privileged != true,allowPrivilegeEscalation != true,capabilities.add ⊆ {NET_BIND_SERVICE}) onRuntimeandBuilder. The API server now short-circuits those attack vectors per CRD apply before the webhook is invoked. Per-container PodSpec iteration stays in the webhook because it exceeds the API server's CEL cost budget. - The same PR also adds two forward-compat regression guards in
pkg/apis/core/v1/podspec_safety_test.go: TestAllTenantContainerSurfacesAreValidatedwalks every CRD root type via reflection and fails if any reachable*apiv1.PodSpecor*apiv1.Containerfield is missing from the hand-maintained known-covered set.TestTenantContainerSurfaces_RejectSysAdminend-to-end exercises each covered surface and assertsValidateForAdmissionrejects aSYS_ADMINinjection at that exact path.
Not addressed in v1.25.0
The advisory's structural recommendation to force capabilities.drop: ["ALL"] at the merge layer is not part of this fix. Fission's own sidecar containers (fission-fetcher, builder) were authored against the OCI default capability
set and need a per-container cap audit before drop:["ALL"] can be applied uniformly. The allowlist on capabilities.add closes the demonstrated CAP_SYS_TIME impact; the OCI-default-cap concern (which the advisory itself marks as
conditional / not demonstrated) is tracked separately.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.24.0"
},
"package": {
"ecosystem": "Go",
"name": "github.com/fission/fission"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.25.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-50570"
],
"database_specific": {
"cwe_ids": [
"CWE-269",
"CWE-732"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-28T20:12:45Z",
"nvd_published_at": "2026-06-10T18:17:13Z",
"severity": "HIGH"
},
"details": "Fission v1.24.0 added PodSpec safety validation for tenant-facing Environment and Function CRDs (`ValidatePodSpecSafety` / `ValidateContainerSafety` admission webhook + `sanitizeContainerSecurityContext` executor merge layer), but the\ncapability check was implemented as a fixed **denylist of six Linux capabilities** (SYS_ADMIN, NET_ADMIN, SYS_PTRACE, SYS_MODULE, DAC_READ_SEARCH, DAC_OVERRIDE). The denylist omitted **CAP_SYS_TIME**, among others. As a result, a tenant\nwho could create a Function or Environment CRD could request `securityContext.capabilities.add: [\"SYS_TIME\"]`, pass Fission\u0027s admission validation and merge-layer sanitization, and run attacker-controlled code with `CAP_SYS_TIME` in the\nresulting function or runtime container.\n\nDemonstrated consequence: cross-tenant node integrity damage via `CAP_SYS_TIME`. The Linux real-time clock is not namespaced \u2014 time namespaces virtualize only `MONOTONIC` and `BOOTTIME`, never `REALTIME` \u2014 so a tenant container holding\n`CAP_SYS_TIME` could call `clock_settime(CLOCK_REALTIME)` and rewrite the shared node wall clock. That corrupts TLS / certificate validity windows, Kubernetes lease renewal, token expiry, scheduling, and time-series for every workload on\nthe node.\n\nThe denylist also omitted `SYS_RAWIO`, `BPF`, `SYS_RESOURCE`, and `MAC_ADMIN`. Those are documented as evidence that the denylist is structurally incomplete (their practical impact is kernel-, LSM-, or device-cgroup-dependent and is not\nexercised in this report).\n\nThe deeper structural problem: a denylist on `capabilities.add` cannot constrain capabilities the OCI runtime grants by default \u2014 `DAC_OVERRIDE` is in the OCI default cap set and reaches the container regardless of any `add` check,\npartially mooting the denylist for its own entries. A capability allowlist (with `drop:[\"ALL\"]` to remove the default set) is the only model that addresses both problems.\n\n### Affected\n\n- Project: `github.com/fission/fission`\n- Versions: `\u003c= 1.24.0`\n- Audited commits: v1.24.0 tag (`ce617120`) and current HEAD at audit time\n- Component: `pkg/apis/core/v1/podspec_safety.go` (`dangerousCapabilities`) and `pkg/executor/util/merge.go` (`dangerousMergeContainerCapabilities`)\n- Pre-condition: cluster does not enforce a restrictive Pod Security Admission (PSA) profile on the function-pod namespace. With PSA `restricted` in force the API server\u0027s PodSecurity admission rejects the pod at creation and this\nfinding does not apply. Fission added its own PodSpec validation precisely because it cannot assume PSA enforcement.\n\n\nFix section (paste into the Fix / Patches field)\n\nFixed in [v1.25.0](https://github.com/fission/fission/releases/tag/v1.25.0) by:\n\n- [PR #3465](https://github.com/fission/fission/pull/3465) (commit [`2569b42b`](https://github.com/fission/fission/commit/2569b42b)) \u2014 replace the denylist with a PSA-restricted allowlist (`NET_BIND_SERVICE` only) at both enforcement\nlayers:\n - `pkg/apis/core/v1/podspec_safety.go` \u2014 `ValidateContainerSafety` now rejects any `capabilities.add` entry not in `allowedCapabilities`. The container check is invoked from `ValidatePodSpecSafety` for every PodSpec container /\ninit-container and from `Environment.validateForAdmission` for the bare `Runtime.Container` / `Builder.Container`.\n - `pkg/executor/util/merge.go` \u2014 `sanitizeContainerSecurityContext` filters `capabilities.add` through the same allowlist at every merge site (poolmgr / newdeploy / container executor / builder).\n- The same PR adds 21 bounded CEL `XValidation` rules covering the cheap pod-level invariants (`hostNetwork` / `hostPID` / `hostIPC` / `serviceAccountName` / `serviceAccount` override) on `FunctionSpec`, `Runtime`, and `Builder`, plus\nthe bare-Container `SecurityContext` checks (`privileged != true`, `allowPrivilegeEscalation != true`, `capabilities.add \u2286 {NET_BIND_SERVICE}`) on `Runtime` and `Builder`. The API server now short-circuits those attack vectors per CRD\napply before the webhook is invoked. Per-container PodSpec iteration stays in the webhook because it exceeds the API server\u0027s CEL cost budget.\n- The same PR also adds two forward-compat regression guards in `pkg/apis/core/v1/podspec_safety_test.go`:\n - `TestAllTenantContainerSurfacesAreValidated` walks every CRD root type via reflection and fails if any reachable `*apiv1.PodSpec` or `*apiv1.Container` field is missing from the hand-maintained known-covered set.\n - `TestTenantContainerSurfaces_RejectSysAdmin` end-to-end exercises each covered surface and asserts `ValidateForAdmission` rejects a `SYS_ADMIN` injection at that exact path.\n\n### Not addressed in v1.25.0\n\nThe advisory\u0027s structural recommendation to force `capabilities.drop: [\"ALL\"]` at the merge layer is **not** part of this fix. Fission\u0027s own sidecar containers (`fission-fetcher`, builder) were authored against the OCI default capability\nset and need a per-container cap audit before `drop:[\"ALL\"]` can be applied uniformly. The allowlist on `capabilities.add` closes the demonstrated `CAP_SYS_TIME` impact; the OCI-default-cap concern (which the advisory itself marks as\nconditional / not demonstrated) is tracked separately.",
"id": "GHSA-qf5v-m7p4-95rp",
"modified": "2026-07-28T20:12:45Z",
"published": "2026-07-28T20:12:45Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/fission/fission/security/advisories/GHSA-qf5v-m7p4-95rp"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-50570"
},
{
"type": "WEB",
"url": "https://github.com/fission/fission/pull/3465"
},
{
"type": "WEB",
"url": "https://github.com/fission/fission/commit/2569b42bfadbcb7d78b55a00a60f77937e522699"
},
{
"type": "PACKAGE",
"url": "https://github.com/fission/fission"
},
{
"type": "WEB",
"url": "https://github.com/fission/fission/releases/tag/v1.25.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption"
}
GHSA-QF8J-85X5-C3WW
Vulnerability from github – Published: 2022-05-24 19:14 – Updated: 2026-08-10 18:31Windows Kernel Elevation of Privilege Vulnerability This CVE ID is unique from CVE-2021-38626.
{
"affected": [],
"aliases": [
"CVE-2021-38625"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-09-15T12:15:00Z",
"severity": "HIGH"
},
"details": "Windows Kernel Elevation of Privilege Vulnerability This CVE ID is unique from CVE-2021-38626.",
"id": "GHSA-qf8j-85x5-c3ww",
"modified": "2026-08-10T18:31:05Z",
"published": "2022-05-24T19:14:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-38625"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-38625"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-38625"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QF96-MMRF-RJ2Q
Vulnerability from github – Published: 2024-01-16 09:30 – Updated: 2024-08-27 18:31Data confidentiality vulnerability in the ScreenReader module. Successful exploitation of this vulnerability may affect service integrity.
{
"affected": [],
"aliases": [
"CVE-2023-52114"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-01-16T09:15:07Z",
"severity": "HIGH"
},
"details": "Data confidentiality vulnerability in the ScreenReader module. Successful exploitation of this vulnerability may affect service integrity.",
"id": "GHSA-qf96-mmrf-rj2q",
"modified": "2024-08-27T18:31:34Z",
"published": "2024-01-16T09:30:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52114"
},
{
"type": "WEB",
"url": "https://consumer.huawei.com/en/support/bulletin/2024/1"
},
{
"type": "WEB",
"url": "https://device.harmonyos.com/en/docs/security/update/security-bulletins-202401-0000001799925977"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-QF9J-6WH9-CXF2
Vulnerability from github – Published: 2022-05-13 01:48 – Updated: 2022-05-13 01:48Privilege escalation vulnerability in INplc-RT 3.08 and earlier allows an attacker with administrator rights to execute arbitrary code on the Windows system via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2018-0671"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-01-09T23:29:00Z",
"severity": "MODERATE"
},
"details": "Privilege escalation vulnerability in INplc-RT 3.08 and earlier allows an attacker with administrator rights to execute arbitrary code on the Windows system via unspecified vectors.",
"id": "GHSA-qf9j-6wh9-cxf2",
"modified": "2022-05-13T01:48:19Z",
"published": "2022-05-13T01:48:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-0671"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/jp/JVN59624986/index.html"
},
{
"type": "WEB",
"url": "http://www.mnc.co.jp/INplc/info_20180907_E.htm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QFCG-7WCX-97QG
Vulnerability from github – Published: 2022-01-12 00:01 – Updated: 2024-11-14 21:31Windows Bind Filter Driver Elevation of Privilege Vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-21858"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-01-11T21:15:00Z",
"severity": "HIGH"
},
"details": "Windows Bind Filter Driver Elevation of Privilege Vulnerability.",
"id": "GHSA-qfcg-7wcx-97qg",
"modified": "2024-11-14T21:31:44Z",
"published": "2022-01-12T00:01:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-21858"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-21858"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-21858"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QFFP-P88C-5R7V
Vulnerability from github – Published: 2022-05-24 17:38 – Updated: 2024-10-08 18:33Windows Update Stack Elevation of Privilege Vulnerability
{
"affected": [],
"aliases": [
"CVE-2021-1694"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-01-12T20:15:00Z",
"severity": "CRITICAL"
},
"details": "Windows Update Stack Elevation of Privilege Vulnerability",
"id": "GHSA-qffp-p88c-5r7v",
"modified": "2024-10-08T18:33:01Z",
"published": "2022-05-24T17:38:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-1694"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-1694"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-1694"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QFFV-M2J8-84WX
Vulnerability from github – Published: 2026-10-12 18:31 – Updated: 2026-10-12 18:31Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 contain an XQuery injection flaw in a deprecated Management API package path. A remote attacker with manage-user-level privileges could exploit this flaw to obtain persistent unauthorized administrative control.
{
"affected": [],
"aliases": [
"CVE-2026-85948"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-12T16:17:06Z",
"severity": "CRITICAL"
},
"details": "Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 contain an XQuery injection flaw in a deprecated Management API package path. A remote attacker with manage-user-level privileges could exploit this flaw to obtain persistent unauthorized administrative control.",
"id": "GHSA-qffv-m2j8-84wx",
"modified": "2026-10-12T18:31:35Z",
"published": "2026-10-12T18:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85948"
},
{
"type": "WEB",
"url": "https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-2026"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QFHR-MXHR-CF29
Vulnerability from github – Published: 2022-05-24 16:46 – Updated: 2024-04-04 00:49A potential incorrect privilege assignment vulnerability exists in the 3rd party pairing mechanism of the Bosch Smart Home Controller (SHC) before 9.8.907 that may result in a restricted app obtaining default app permissions. In order to exploit the vulnerability, the adversary needs to have successfully paired an app, which requires user interaction.
{
"affected": [],
"aliases": [
"CVE-2019-11896"
],
"database_specific": {
"cwe_ids": [
"CWE-269",
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-05-29T21:29:00Z",
"severity": "HIGH"
},
"details": "A potential incorrect privilege assignment vulnerability exists in the 3rd party pairing mechanism of the Bosch Smart Home Controller (SHC) before 9.8.907 that may result in a restricted app obtaining default app permissions. In order to exploit the vulnerability, the adversary needs to have successfully paired an app, which requires user interaction.",
"id": "GHSA-qfhr-mxhr-cf29",
"modified": "2024-04-04T00:49:24Z",
"published": "2022-05-24T16:46:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-11896"
},
{
"type": "WEB",
"url": "https://psirt.bosch.com/Advisory/BOSCH-SA-662084.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-QFM4-FR7V-VGGM
Vulnerability from github – Published: 2022-05-24 17:35 – Updated: 2025-08-29 00:31, aka 'Windows Backup Engine Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2020-16958, CVE-2020-16959, CVE-2020-16960, CVE-2020-16961, CVE-2020-16963, CVE-2020-16964.
{
"affected": [],
"aliases": [
"CVE-2020-16962"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-12-10T00:15:00Z",
"severity": "HIGH"
},
"details": ", aka \u0027Windows Backup Engine Elevation of Privilege Vulnerability\u0027. This CVE ID is unique from CVE-2020-16958, CVE-2020-16959, CVE-2020-16960, CVE-2020-16961, CVE-2020-16963, CVE-2020-16964.",
"id": "GHSA-qfm4-fr7v-vggm",
"modified": "2025-08-29T00:31:12Z",
"published": "2022-05-24T17:35:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-16962"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-16962"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16962"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-1
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Mitigation MIT-48
Strategy: Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Mitigation MIT-49
Strategy: Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
CAPEC-122: Privilege Abuse
An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources.
CAPEC-233: Privilege Escalation
An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform.
CAPEC-58: Restful Privilege Elevation
An adversary identifies a Rest HTTP (Get, Put, Delete) style permission method allowing them to perform various malicious actions upon server data due to lack of access control mechanisms implemented within the application service accepting HTTP messages.