# CVE-2023-0482: Insecure Temporary File in RESTEasy > Local attackers can read sensitive temporary files created by RESTEasy due to insecure file permissions. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/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:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Feb 2023 - **Updated:** 18 Mar 2025 - **Also known as:** DEBIAN-CVE-2023-0482, GHSA-2c6g-pfx3-w7h8, UBUNTU-CVE-2023-0482 ## What is CVE-2023-0482? CVE-2023-0482 is a medium-severity vulnerability in Netapp Active Iq Unified Manager, published on 17 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In RESTEasy the insecure File.createTempFile() is used in the DataSourceProvider, FileProvider and Mime4JWorkaround classes which creates temp files with insecure permissions that could be read by a local user. Weakness: CWE-378 (Creation of Temporary File With Insecure Permissions) ## Which versions are affected by CVE-2023-0482? 16 open source packages ship an affected version, including org.jboss.resteasy:resteasy-core and org.jboss.resteasy:resteasy-multipart-provider. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.jboss.resteasy:resteasy-core` | Maven | All versions | 3.15.5.Final | | `org.jboss.resteasy:resteasy-core` | Maven | All versions | 3.15.5.Final | | `org.jboss.resteasy:resteasy-core` | Maven | From 4.0.0.Beta1 | 4.7.8.Final | | `org.jboss.resteasy:resteasy-core` | Maven | From 4.0.0.Beta1 | 4.7.8.Final | | `org.jboss.resteasy:resteasy-core` | Maven | From 5.0.0.Alpha1 | 5.0.6.Final | | `org.jboss.resteasy:resteasy-core` | Maven | From 5.0.0.Alpha1 | 5.0.6.Final | | `org.jboss.resteasy:resteasy-core` | Maven | From 6.0.0.Beta1 | 6.2.3.Final | | `org.jboss.resteasy:resteasy-core` | Maven | From 6.0.0.Beta1 | 6.2.3.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | All versions | 3.15.5.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | All versions | 3.15.5.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | From 4.0.0.Beta1 | 4.7.8.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | From 4.0.0.Beta1 | 4.7.8.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | From 5.0.0.Alpha1 | 5.0.6.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | From 5.0.0.Alpha1 | 5.0.6.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | From 6.0.0.Beta1 | 6.2.3.Final | | `org.jboss.resteasy:resteasy-multipart-provider` | Maven | From 6.0.0.Beta1 | 6.2.3.Final | Products: Netapp Active Iq Unified Manager, Netapp Oncommand Workflow Automation, Redhat Resteasy. ## How do I fix CVE-2023-0482? Upgrade org.jboss.resteasy:resteasy-core to a fixed version for your release line: 3.15.5.Final, 4.7.8.Final, 5.0.6.Final or 6.2.3.Final. ## Is CVE-2023-0482 being exploited? There is no known exploitation of CVE-2023-0482 in the wild and no public exploit code. Public exploit code: - Cybersecurity vulnerability analysis of CVE-2023-0482, including NVD details, patch information, Cyber Kill Chain mapping, and mitigation recommendations (github_poc): https://github.com/Bethel904/CVE-2023-0482-Analysis ## Other vulnerabilities in Netapp Active Iq Unified Manager - [CVE-2022-31692](https://insights.sbomify.com/CVE-2022-31692/): Spring Security authorization rules can be bypassed via forward or include dispatcher types (critical 9.8) - [CVE-2022-2526](https://insights.sbomify.com/CVE-2022-2526/): Use after free in systemd-resolved (critical 9.8) - [CVE-2022-22978](https://insights.sbomify.com/CVE-2022-22978/): Authorization bypass in Spring Security (critical 9.8) - [CVE-2021-22931](https://insights.sbomify.com/CVE-2021-22931/): Code injection in Node (critical 9.8) - [CVE-2018-2938](https://insights.sbomify.com/CVE-2018-2938/): Code injection in Java (critical 9.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-0482 and fix it if it is affected. What it is: CVE-2023-0482 is a medium-severity vulnerability in Netapp Active Iq Unified Manager, published on 17 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-0482 in the wild and no public exploit code. Affected packages and fixed versions: - org.jboss.resteasy:resteasy-core (Maven): affected all versions; fixed in 3.15.5.Final - org.jboss.resteasy:resteasy-core (Maven): affected all versions; fixed in 3.15.5.Final - org.jboss.resteasy:resteasy-core (Maven): affected from 4.0.0.Beta1; fixed in 4.7.8.Final - org.jboss.resteasy:resteasy-core (Maven): affected from 4.0.0.Beta1; fixed in 4.7.8.Final - org.jboss.resteasy:resteasy-core (Maven): affected from 5.0.0.Alpha1; fixed in 5.0.6.Final - org.jboss.resteasy:resteasy-core (Maven): affected from 5.0.0.Alpha1; fixed in 5.0.6.Final - org.jboss.resteasy:resteasy-core (Maven): affected from 6.0.0.Beta1; fixed in 6.2.3.Final - org.jboss.resteasy:resteasy-core (Maven): affected from 6.0.0.Beta1; fixed in 6.2.3.Final - org.jboss.resteasy:resteasy-multipart-provider (Maven): affected all versions; fixed in 3.15.5.Final - org.jboss.resteasy:resteasy-multipart-provider (Maven): affected all versions; fixed in 3.15.5.Final - org.jboss.resteasy:resteasy-multipart-provider (Maven): affected from 4.0.0.Beta1; fixed in 4.7.8.Final - org.jboss.resteasy:resteasy-multipart-provider (Maven): affected from 4.0.0.Beta1; fixed in 4.7.8.Final 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-0482/ (Markdown: https://insights.sbomify.com/CVE-2023-0482/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-0482 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-0482 - OSV: https://osv.dev/vulnerability/CVE-2023-0482 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-0482/ Summaries are generated and may contain mistakes; the official description above is the record.