# CVE-2024-41995: Initialization of a resource with an insecure default vulnerability exists in JavaTM Platform Ver.12.89 and earlier.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Aug 2024
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-qxhm-3vp2-fcq3

## What is CVE-2024-41995?

CVE-2024-41995 is a high-severity vulnerability in Ricoh Company, Ltd. JavaTM Platform, published on 6 Aug 2024. 

### Official description

Initialization of a resource with an insecure default vulnerability exists in JavaTM Platform Ver.12.89 and earlier. If this vulnerability is exploited, the product may be affected by some known TLS1.0 and TLS1.1 vulnerabilities. As for the specific products/models/versions of MFPs and printers that contain JavaTM Platform, see the information provided by the vendor.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2024-41995?


## How do I fix CVE-2024-41995?

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

## Is CVE-2024-41995 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41995 and fix it if it is affected.

What it is: CVE-2024-41995 is a high-severity vulnerability in Ricoh Company, Ltd. JavaTM Platform, published on 6 Aug 2024. 
Exploitation: There is no known exploitation of CVE-2024-41995 in the wild and no public exploit code.

Affected product: Ricoh Company, Ltd. JavaTM Platform. 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-2024-41995/ (Markdown: https://insights.sbomify.com/CVE-2024-41995/index.md)
```

## Sources

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

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