UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Any install that has UNEDITABLESCHEMAS and/or UNEDITABLETABLEDESCRIPTIONMATCHRULES 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 amundsen-security@lists.lfaidata.foundation More details Summary: I believe that UNEDITABLESCHEMAS and UNEDITABLETABLEDESCRIPTIONMATCHRULES 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: 1. docker-compose -f docker-amundsen.yml up neo4j elasticsearch amundsensearch amundsenmetadata 2. python example/scripts/sampledataloader.py 3.…

Published by the source

2 Dec 2020, 18:28 UTC

Last modified by the source

2 Dec 2024, 05:46 UTC

Source last checked

26 Oct 2026, 13:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-47qg-q58v-7vrp

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-47qg-q58v-7vrp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-47qg-q58v-7vrp

Advisory: UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend
IDs: GHSA-47qg-q58v-7vrp
Record: https://patchnext.com/advisories/ghsa-47qg-q58v-7vrp (revision 2, source checked 26 Oct 2026, 13:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: amundsen-frontend 3.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI amundsen-frontend: affected >= 2.3.0, <= 2.3.0; >= 3.0.0, <= 3.0.0; fixed in 3.1.0

## Suggested inspection (read-only)
- `python -m pip show amundsen-frontend`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on amundsen-frontend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-47qg-q58v-7vrp (OSV record GHSA-47qg-q58v-7vrp lists affected ranges: PyPI amundsen-frontend >=2.3.0 =3.0.0 <3.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-47qg-q58v-7vrp (GitHub-reviewed advisory GHSA-47qg-q58v-7vrp lists affected ranges: PyPI amundsen-frontend >=2.3.0 =3.0.0 <=3.0.0)

Commands are suggestions: review each one before running it.