# CVE-2023-23344: HCL BigFix WebUI Insights is susceptible to a lack of sufficient authorization

> An authenticated unprivileged operator can access administrator pages in HCL BigFix WebUI Insights due to insufficient authorization checks.

- **Severity:** Low 3.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jun 2023
- **Updated:** 8 Nov 2024
- **Also known as:** GHSA-4w5p-7c62-6g92

## What is CVE-2023-23344?

CVE-2023-23344 is a low-severity missing authorization vulnerability in HCL BigFix WebUI Insights, published on 23 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A permission issue in BigFix WebUI Insights site version 14 allows an authenticated, unprivileged operator to access an administrator page.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-23344?

It affects 1 product.


Products: Hcltech Bigfix Webui Insights.

## How do I fix CVE-2023-23344?

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

## Is CVE-2023-23344 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23344 and fix it if it is affected.

What it is: CVE-2023-23344 is a low-severity missing authorization vulnerability in HCL BigFix WebUI Insights, published on 23 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-23344 in the wild and no public exploit code.

Affected product: HCL BigFix WebUI Insights. 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-2023-23344/ (Markdown: https://insights.sbomify.com/CVE-2023-23344/index.md)
```

## Sources

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

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