{"answers":{"affected":"2 open source packages ship an affected version, including io.quarkus.resteasy.reactive:resteasy-reactive-common. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-0481 in the wild and no public exploit code.","fix":"Upgrade io.quarkus.resteasy.reactive:resteasy-reactive-common to 3.0.0.Alpha4 or later.","what":"CVE-2023-0481 is a low-severity vulnerability in Quarkus, published on 24 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-0481 and fix it if it is affected.\n\nWhat it is: CVE-2023-0481 is a low-severity vulnerability in Quarkus, published on 24 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-0481 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.quarkus.resteasy.reactive:resteasy-reactive-common (Maven): affected all versions; fixed in 3.0.0.Alpha4\n- io.quarkus.resteasy.reactive:resteasy-reactive-common (Maven): affected all versions; fixed in 3.0.0.Alpha4\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-0481/ (Markdown: https://insights.sbomify.com/CVE-2023-0481/index.md)","id":"CVE-2023-0481","markdown":"https://insights.sbomify.com/CVE-2023-0481/index.md","name":"CVE-2023-0481","record":{"aliases":["GHSA-j75r-vf64-6rrh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Quarkus framework","requires_auth":"low_privilege","summary":"Local attackers can read sensitive temporary files created by Quarkus RestEasy Reactive due to insecure file permissions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quarkus","vendor":"quarkus"}],"cvss":{"score":3.3,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"},{"id":"CWE-378","name":"Creation of Temporary File With Insecure Permissions"}],"description":"In RestEasy Reactive implementation of Quarkus the insecure File.createTempFile() is used in the FileBodyHandler class which creates temp files with insecure permissions that could be read by a local user.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"RestEasy Reactive implementation of Quarkus allows Creation of Temporary File With Insecure Permissions","id":"CVE-2023-0481","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":1,"next":{"headline":"Insecure Temporary File in RESTEasy","id":"CVE-2023-0482"},"packages":[{"ecosystem":"Maven","fixed":["3.0.0.Alpha4"],"introduced":["0"],"last_affected":[],"package":"io.quarkus.resteasy.reactive:resteasy-reactive-common","purl":null,"source":"GHSA-j75r-vf64-6rrh"},{"ecosystem":"Maven","fixed":["3.0.0.Alpha4"],"introduced":["0"],"last_affected":[],"package":"io.quarkus.resteasy.reactive:resteasy-reactive-common","purl":"pkg:maven/io.quarkus.resteasy.reactive/resteasy-reactive-common","source":"GHSA-j75r-vf64-6rrh"}],"prev":{"headline":"Cross-site request forgery in VitalPBX","id":"CVE-2023-0480"},"products":["Quarkus"],"published":"2023-02-24","related":[{"cvss_score":9.8,"headline":"Code injection in quarkus dev ui config editor","id":"CVE-2022-4116","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":9.8,"headline":"Quarkus does not terminate HTTP requests header context","id":"CVE-2022-2466","kev_date_added":null,"published":"2022-08-31"},{"cvss_score":9.1,"headline":"Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass","id":"CVE-2024-12225","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":8.8,"headline":"Quarkus authorization bypass via semicolon path normalization inconsistency","id":"CVE-2026-39852","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.8,"headline":"Privilege escalation in quarkus","id":"CVE-2022-0981","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":8.6,"headline":"Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.","id":"CVE-2023-6267","kev_date_added":null,"published":"2024-01-25"},{"cvss_score":8.1,"headline":"Quarkus: http security policy bypass","id":"CVE-2023-4853","kev_date_added":null,"published":"2023-09-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-12","vendors":["n/a"]},"summary":"Local attackers can read sensitive temporary files created by Quarkus RestEasy Reactive due to insecure file permissions.","url":"https://insights.sbomify.com/CVE-2023-0481/"}