# CVE-2019-6961: Missing authorization in n/a

> A logged-in user can modify privileged network configurations like DDNS and QoS by bypassing access controls in the RDK WebUI backend.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xm7h-r43h-8xg2

## What is CVE-2019-6961?

CVE-2019-6961 is a medium-severity missing authorization vulnerability in n/a, published on 20 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect access control in actionHandlerUtility.php in the RDK RDKB-20181217-1 WebUI module allows a logged in user to control DDNS, QoS, RIP, and other privileged configurations (intended only for the network operator) by sending an HTTP POST to the PHP backend, because the page filtering for non-superuser (in header.php) is done only for GET requests and not for direct AJAX calls.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2019-6961?

It affects 1 product.


Products: Rdkcentral Rdkb Ccsppandm.

## How do I fix CVE-2019-6961?

No fix has been published for CVE-2019-6961 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-6961 being exploited?

There is no known exploitation of CVE-2019-6961 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-6963](https://insights.sbomify.com/CVE-2019-6963/): Memory corruption in n/a (high 8.8)
- [CVE-2019-6964](https://insights.sbomify.com/CVE-2019-6964/): Memory corruption in n/a (high 8.8)
- [CVE-2019-6962](https://insights.sbomify.com/CVE-2019-6962/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6961 and fix it if it is affected.

What it is: CVE-2019-6961 is a medium-severity missing authorization vulnerability in n/a, published on 20 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6961 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-6961/ (Markdown: https://insights.sbomify.com/CVE-2019-6961/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-6961
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-6961
- OSV: https://osv.dev/vulnerability/CVE-2019-6961

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-6961/
Summaries are generated and may contain mistakes; the official description above is the record.