{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12147 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12147 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12147 is a medium-severity vulnerability in floragunn Search Guard FLX, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12147 and fix it if it is affected.\n\nWhat it is: CVE-2025-12147 is a medium-severity vulnerability in floragunn Search Guard FLX, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12147 in the wild and no public exploit code.\n\nAffected product: floragunn Search Guard FLX. 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-2025-12147/ (Markdown: https://insights.sbomify.com/CVE-2025-12147/index.md)","id":"CVE-2025-12147","markdown":"https://insights.sbomify.com/CVE-2025-12147/index.md","name":"CVE-2025-12147","record":{"aliases":["GHSA-5pcq-rjhv-m338"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Search Guard FLX","requires_auth":"low_privilege","summary":"Attackers can bypass Field-Level Security to read protected object members in Search Guard FLX, exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"floragunn","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Search Guard FLX versions 3.1.1 and earlier, Field-Level Security (FLS) rules are improperly enforced on object-valued fields.\n\nWhen an FLS exclusion rule (e.g., ~field) is applied to a field which contains an object as its value, the object is correctly removed from the _source returned by search operations. However, the object members (i.e., child attributes) remain accessible to search queries. This exposure allows adversaries to infer or reconstruct the original contents of the excluded object.\n\nWorkaround - If you cannot upgrade immediately and FLS exclusion rules are used for object valued attributes (like ~object), add an additional exclusion rule for the members of the object (like ~object.*).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Unauthorized access to fields protected by Field-Level Security (FLS) when those fields are members of an object","id":"CVE-2025-12147","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Unauthorized access to fields protected by Field Masking (FM) for fields of type IP","id":"CVE-2025-12148"},"packages":[],"prev":{"headline":"Stack Memory Corruption Vulnerability","id":"CVE-2025-12143"},"products":["Search Guard FLX"],"published":"2025-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-10-29","vendors":["floragunn"]},"summary":"Attackers can bypass Field-Level Security to read protected object members in Search Guard FLX, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2025-12147/"}