# CVE-2023-27096: Hippo4j allows attacker to obtain sensitive info via ConfigVerifyController function of Tenant Management module

> An attacker can obtain sensitive information via the ConfigVerifyController in the Tenant Management module of Hippo4j.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 27 Mar 2023
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-h855-6hph-v363

## What is CVE-2023-27096?

CVE-2023-27096 is a medium-severity vulnerability in n/a, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure Permissions vulnerability found in OpenGoofy Hippo4j v.1.4.3 allows attacker to obtain sensitive information via the ConfigVerifyController function of the Tenant Management module.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

2 open source packages ship an affected version, including cn.hippo4j:hippo4j-all. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cn.hippo4j:hippo4j-all` | Maven | All versions to 1.4.3 | None |
| `cn.hippo4j:hippo4j-all` | Maven | All versions to 1.4.3 | None |

Products: Opengoofy Hippo4j.

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

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

## Is CVE-2023-27096 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27094](https://insights.sbomify.com/CVE-2023-27094/): Hippo4j privilege escalation issue (high 8.8)
- [CVE-2023-27095](https://insights.sbomify.com/CVE-2023-27095/): Exposure of Sensitive Information in OpenGoofy Hippo4j (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27096 is a medium-severity vulnerability in n/a, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27096 in the wild and no public exploit code.

Affected packages and fixed versions:
- cn.hippo4j:hippo4j-all (Maven): affected all versions up to 1.4.3; no fix listed
- cn.hippo4j:hippo4j-all (Maven): affected all versions up to 1.4.3; no fix listed

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-27096/ (Markdown: https://insights.sbomify.com/CVE-2023-27096/index.md)
```

## Sources

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

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