{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-28442 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-28442 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-28442 is a high-severity vulnerability in geonode, published on 23 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-28442 and fix it if it is affected.\n\nWhat it is: CVE-2023-28442 is a high-severity vulnerability in geonode, published on 23 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-28442 in the wild and no public exploit code.\n\nAffected product: geonode. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-28442/ (Markdown: https://insights.sbomify.com/CVE-2023-28442/index.md)","id":"CVE-2023-28442","markdown":"https://insights.sbomify.com/CVE-2023-28442/index.md","name":"CVE-2023-28442","record":{"aliases":["GHSA-87mh-vw7c-5v6w"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"GeoNode geospatial platform","requires_auth":"none","summary":"Anonymous users can access sensitive GeoNode configuration data via an exposed GeoServer REST endpoint due to specific integration settings.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"geonode","vendor":"geosolutionsgroup"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"GeoNode is an open source platform that facilitates the creation, sharing, and collaborative use of geospatial data. Prior to versions 2.20.6, 2.19.6, and 2.18.7, anonymous users can obtain sensitive information about GeoNode configurations from the response of the `/geoserver/rest/about/status` Geoserver REST API endpoint. The Geoserver endpoint is secured by default, but the configuration of Geoserver for GeoNode opens a list of REST endpoints to support some of its public-facing services. The vulnerability impacts both GeoNode 3 and GeoNode 4 instances.\n\nGeoserver security configuration is provided by `geoserver-geonode-ext`. A patch for 2.20.7 has been released which blocks access to the affected endpoint. The patch has been backported to branches 2.20.6, 2.19.7, 2.19.6, and 2.18.7. All the published artifacts and Docker images have been updated accordingly. A more advanced patch has been applied to the master and development versions, which require some changes to GeoNode code. They will be available with the next 4.1.0 release. The patched configuration only has an effect on new deployments. For existing setups, the patch must be applied manually inside the Geoserver data directory. The patched file must replace the existing `\u003cgeoserver_datadir\u003e/security/rest.properties` file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Geoserver for GeoNode sensitive information leak","id":"CVE-2023-28442","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"directus vulnerable to Insertion of Sensitive Information into Log File","id":"CVE-2023-28443"},"packages":[],"prev":{"headline":"smartCARS 3 Password Stored as plain text in Error Log","id":"CVE-2023-28441"},"products":["geonode"],"published":"2023-03-23","related":[{"cvss_score":7.5,"headline":"GeoNode SSRF Bypass to return internal host data","id":"CVE-2023-42439","kev_date_added":null,"published":"2023-09-15"},{"cvss_score":7.5,"headline":"Geonode Server Side Request Forgery vulnerability","id":"CVE-2023-40017","kev_date_added":null,"published":"2023-08-24"},{"cvss_score":6.5,"headline":"XML External Entity (XXE) injection in GeoServer style upload functionality","id":"CVE-2023-26043","kev_date_added":null,"published":"2023-02-27"},{"cvss_score":6.1,"headline":"GeoNode stored XSS to full account takeover","id":"CVE-2024-27091","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":5.3,"headline":"GeoNode \u003c 4.4.5, 5.0.2 SSRF via Document Upload","id":"CVE-2026-39921","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":5.3,"headline":"GeoNode SSRF via Service Registration","id":"CVE-2026-39922","kev_date_added":null,"published":"2026-04-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-25","vendors":["GeoNode"]},"summary":"Anonymous users can access sensitive GeoNode configuration data via an exposed GeoServer REST endpoint due to specific integration settings.","url":"https://insights.sbomify.com/CVE-2023-28442/"}