GHSA-47qg-q58v-7vrp
Fix: amundsen-io/amundsenfrontendlibrary@0b47694GHSA-47qg-q58v-7vrp is a security vulnerability in amundsen-frontend. O3 Security confirms whether GHSA-47qg-q58v-7vrp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend
Real-World Exposure
amundsen-frontend🐍amundsen-frontendReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Any 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.
Patches
There is an attached PR that applies this restriction on the back-end.
Workarounds
N/A
References
N/A
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
More details
Summary: I believe that UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES are only being applied on the front-end, not on the frontend service back-end, allowing any user to modify table and column descriptions even if this configuration parameter is set.
Repro steps:
- docker-compose -f docker-amundsen.yml up neo4j elasticsearch amundsensearch amundsenmetadata
- python example/scripts/sample_data_loader.py
- FRONTEND_SVC_CONFIG_MODULE_CLASS=amundsen_application.config.TestConfig PYTHONPATH=. python3 amundsen_application/wsgi.py
- Attempt a modification to a table description:
curl 'http://localhost:5000/api/metadata/v0/put_table_description' \\ -X 'PUT' \\ -H 'Content-Type: application/json;charset=UTF-8' \\ --data-binary '{"description":"2t test table","key":"hive://gold.test_schema/test_table1","source":"user"}' {"msg":"Success"}
- This correctly succeeds, which can be validated by GETing the info:
curl 'http://localhost:5000/api/metadata/v0/get_table_description?key=hive://gold.test_schema/test_table1' {"description":"1st test table","msg":"Success"}
At this point, modify TestConfig inside config.py to add this line: UNEDITABLE_SCHEMAS = set(['test_schema'])
You can now re-run step 4, and step 5 with different data, and confirm that the modification has persisted. If you build and run the UI, you can see that on the page http://localhost:5000/table_detail/gold/hive/test_schema/test_table1 http://localhost:5000/table_detail/gold/hive/test_schema/test_table1, the inline editor is correctly disabled.
Looking at amundsenfrontendlibrary/amundsen_application/api/metadata/v0.py:268 put_table_description, you can see there's no reference to UNEDITABLE_SCHEMAS or UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES.
The only place I can find these referenced is in amundsenfrontendlibrary/amundsen_application/api/utils/metadata_utils.py:marshall_table_full, which would explain why the UI is correctly respecting this setting.
If this is correct, put_column_description would also be similarly affected.
I believe the correct fix for all of these methods is to load the table, run it through marshall_dashboard_partial to fully evaluate what's editable or not (to reuse the same code path for FE and back-end), and reject the response if it's not editable. I'll implement a fix along these lines once someone confirms this.
History: This functionality was introduced in https://github.com/amundsen-io/amundsenfrontendlibrary/pull/497/files https://github.com/amundsen-io/amundsenfrontendlibrary/pull/497 on July 9, corresponding to the 2.3.0 release of amundsenfrontend. That release was introduced into the main repo dockerfile on October 28 in https://github.com/amundsen-io/amundsen/pull/785 https://github.com/amundsen-io/amundsen/pull/785
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | amundsen-frontend | ≥ 2.3.0&&< 3.1.0 | 3.1.0 |
| 🐍PyPI | amundsen-frontend | ≥ 3.0.0&&< 3.1.0 | 3.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for amundsen-frontend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update amundsen-frontend to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-47qg-q58v-7vrp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-47qg-q58v-7vrp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-47qg-q58v-7vrp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-47qg-q58v-7vrp in your dependencies?
O3 detects GHSA-47qg-q58v-7vrp across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.