{"answers":{"affected":"4 open source packages ship an affected version, including amundsen-frontend.","exploited":"There is no known exploitation of GHSA-47qg-q58v-7vrp in the wild and no public exploit code.","fix":"Upgrade amundsen-frontend to 3.1.0 or later.","what":"GHSA-47qg-q58v-7vrp is a missing authorization vulnerability in amundsen-frontend, published on 2 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-47qg-q58v-7vrp and fix it if it is affected.\n\nWhat it is: GHSA-47qg-q58v-7vrp is a missing authorization vulnerability in amundsen-frontend, published on 2 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-47qg-q58v-7vrp in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- amundsen-frontend (PyPI): affected from 2.3.0; fixed in 3.1.0\n- amundsen-frontend (PyPI): affected from 2.3.0; fixed in 3.1.0\n- amundsen-frontend (PyPI): affected from 3.0.0; fixed in 3.1.0\n- amundsen-frontend (PyPI): affected from 3.0.0; fixed in 3.1.0\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/GHSA-47qg-q58v-7vrp/ (Markdown: https://insights.sbomify.com/GHSA-47qg-q58v-7vrp/index.md)","id":"GHSA-47qg-q58v-7vrp","markdown":"https://insights.sbomify.com/GHSA-47qg-q58v-7vrp/index.md","name":"GHSA-47qg-q58v-7vrp","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Amundsen data catalog","requires_auth":"low_privilege","summary":"Attackers can modify table and column descriptions in Amundsen despite backend configuration restrictions, bypassing intended data integrity controls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nAny install that has `UNEDITABLE_SCHEMAS` and/or `UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES` set in the front-end, is being impacted. The value of these properties is ignored if set, allowing any user to modify table and column descriptions, even though the properties imply they shouldn't be.\n\n### Patches\nThere is an attached PR that applies this restriction on the back-end.\n\n### Workarounds\nN/A\n\n### References\nN/A\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Email us at [amundsen-security@lists.lfaidata.foundation](mailto:amundsen-security@lists.lfaidata.foundation)\n\n### More details\nSummary: I believe that UNEDITABLE_SCHEMAS and\nUNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES are only being applied on the\nfront-end, not on the frontend service back-end, allowing any user to\nmodify table and column descriptions even if this configuration parameter\nis set.\n\nRepro steps:\n\n1. docker-compose -f docker-amundsen.yml up neo4j elasticsearch\namundsensearch amundsenmetadata\n2. python example/scripts/sample_data_loader.py\n3. FRONTEND_SVC_CONFIG_MODULE_CLASS=amundsen_application.config.TestConfig\nPYTHONPATH=. python3 amundsen_application/wsgi.py\n4. Attempt a modification to a table description:\n\ncurl '\u003chttp://localhost:5000/api/metadata/v0/put_table_description\u003e' \\\\\\\\\n-X 'PUT' \\\\\\\\\n-H 'Content-Type: application/json;charset=UTF-8' \\\\\\\\\n--data-binary '{\"description\":\"2t test table\",\"key\":\"hive://gold.test_schema/test_table1\",\"source\":\"user\"}'\n{\"msg\":\"Success\"}\n\n5. This correctly succeeds, which can be validated by GETing the info:\n\ncurl '\u003chttp://localhost:5000/api/metadata/v0/get_table_description?key=hive://gold.test_schema/test_table1\u003e'\n{\"description\":\"1st test table\",\"msg\":\"Success\"}\n\nAt this point, modify TestConfig inside config.py to add this line: UNEDITABLE_SCHEMAS\n= set(['test_schema'])\n\nYou can now re-run step 4, and step 5 with different data, and confirm\nthat the modification has persisted. If you build and run the UI, you can\nsee that on the page\n\u003chttp://localhost:5000/table_detail/gold/hive/test_schema/test_table1\u003e\nhttp://localhost:5000/table_detail/gold/hive/test_schema/test_table1, the\ninline editor is correctly disabled.\n\nLooking at\namundsenfrontendlibrary/amundsen_application/api/metadata/v0.py:268\nput_table_description, you can see there's no reference to\nUNEDITABLE_SCHEMAS or UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES.\n\nThe only place I can find these referenced is in\namundsenfrontendlibrary/amundsen_application/api/utils/metadata_utils.py:marshall_table_full,\nwhich would explain why the UI is correctly respecting this setting.\n\nIf this is correct, put_column_description would also be similarly\naffected.\n\nI believe the correct fix for all of these methods is to load the table,\nrun it through marshall_dashboard_partial to fully evaluate what's\neditable or not (to reuse the same code path for FE and back-end), and\nreject the response if it's not editable. I'll implement a fix along these\nlines once someone confirms this.\n\nHistory: This functionality was introduced in\n\u003chttps://github.com/amundsen-io/amundsenfrontendlibrary/pull/497/files\u003e\nhttps://github.com/amundsen-io/amundsenfrontendlibrary/pull/497 on July\n9, corresponding to the 2.3.0 release of amundsenfrontend. That release was\nintroduced into the main repo dockerfile on October 28 in\n\u003chttps://github.com/amundsen-io/amundsen/pull/785\u003e\nhttps://github.com/amundsen-io/amundsen/pull/785","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend","id":"GHSA-47qg-q58v-7vrp","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["3.1.0"],"introduced":["2.3.0"],"last_affected":[],"package":"amundsen-frontend","purl":null,"source":"GHSA-47qg-q58v-7vrp"},{"ecosystem":"PyPI","fixed":["3.1.0"],"introduced":["2.3.0"],"last_affected":[],"package":"amundsen-frontend","purl":"pkg:pypi/amundsen-frontend","source":"GHSA-47qg-q58v-7vrp"},{"ecosystem":"PyPI","fixed":["3.1.0"],"introduced":["3.0.0"],"last_affected":[],"package":"amundsen-frontend","purl":null,"source":"GHSA-47qg-q58v-7vrp"},{"ecosystem":"PyPI","fixed":["3.1.0"],"introduced":["3.0.0"],"last_affected":[],"package":"amundsen-frontend","purl":"pkg:pypi/amundsen-frontend","source":"GHSA-47qg-q58v-7vrp"}],"products":null,"published":"2020-12-02","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can modify table and column descriptions in Amundsen despite backend configuration restrictions, bypassing intended data integrity controls.","url":"https://insights.sbomify.com/GHSA-47qg-q58v-7vrp/"}