fix(deps): update dependency @backstage/plugin-app-backend to v0.3.75 [security] #2294
+264
−11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.github.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/npm-backstage-plugin-app-backend-vulnerability
branch
15 times, most recently
from
cad79b1
to
2f2b91b
Compare
… [security] Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/npm-backstage-plugin-app-backend-vulnerability
branch
from
2f2b91b
to
1841023
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.3.71->0.3.75GitHub Vulnerability Alerts
CVE-2024-47762
Impact
Configuration supplied through
APP_CONFIG_*environment variables, for exampleAPP_CONFIG_backend_listen_port=7007, where unexpectedly ignoring the visibility defined in configuration schema. This occurred even if the configuration schema specified that they should have backend or secret visibility. This was an intended feature of theAPP_CONFIG_*way of supplying configuration, but now clearly goes against the expected behavior of the configuration system. This behavior leads to a risk of potentially exposing sensitive configuration details intended to remain private or restricted to backend processes.Patches
The issue has been resolved in version
0.3.75of the@backstage/plugin-app-backendpackage. Users are encouraged to upgrade to this version to mitigate the vulnerability.Workarounds
As a temporary measure, avoid supplying secrets using the
APP_CONFIG_configuration pattern. Consider alternative methods for setting secrets, such as the environment substitution available for Backstage configuration.References
If you have any questions or comments about this advisory:
Open an issue in the Backstage repository
Visit our Discord, linked to in Backstage README
Unexpected visibility of environment variable configurations in @backstage/plugin-app-backend
CVE-2024-47762 / GHSA-qc4v-xq2m-65wc
More information
Details
Impact
Configuration supplied through
APP_CONFIG_*environment variables, for exampleAPP_CONFIG_backend_listen_port=7007, where unexpectedly ignoring the visibility defined in configuration schema. This occurred even if the configuration schema specified that they should have backend or secret visibility. This was an intended feature of theAPP_CONFIG_*way of supplying configuration, but now clearly goes against the expected behavior of the configuration system. This behavior leads to a risk of potentially exposing sensitive configuration details intended to remain private or restricted to backend processes.Patches
The issue has been resolved in version
0.3.75of the@backstage/plugin-app-backendpackage. Users are encouraged to upgrade to this version to mitigate the vulnerability.Workarounds
As a temporary measure, avoid supplying secrets using the
APP_CONFIG_configuration pattern. Consider alternative methods for setting secrets, such as the environment substitution available for Backstage configuration.References
If you have any questions or comments about this advisory:
Open an issue in the Backstage repository
Visit our Discord, linked to in Backstage README
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
backstage/backstage (@backstage/plugin-app-backend)
v0.3.75Compare Source
Patch Changes
094eaa3: Remove references to in-repo backend-commonv0.3.74Compare Source
Patch Changes
72a8c7b: Return HTTP status 400 rather than 500 when receiving an unknown POST request.d3f79d1: Fixing dependency metadata with the new@backstage/plugin-apppackage590fb2d: BREAKING: The app backend now supports the newindex.html.tmploutput from@backstage/cli. If available, theindex.htmlwill be templated at runtime with the current configuration of the app backend.This is marked as a breaking change because you must now supply the app build-time configuration to the backend. This change also affects the public path behavior, where it is no longer necessary to build the app with the correct public path upfront. You now only need to supply a correct
app.baseUrlto the app backend plugin at runtime.An effect that this change has is that the
index.htmlwill now contain and present the frontend configuration in an easily readable way, which can aid in debugging. This data was always available in the frontend, but it was injected and hidden in the static bundle.This templating behavior is enabled by default, but it can be disabled by setting the
app.disableConfigInjectionconfiguration option totrue.d425fc4: Modules, plugins, and services are nowBackendFeature, not a function that returns a feature.c2b63ab: Updated dependencysupertestto^7.0.0.Updated dependencies
v0.3.73Compare Source
v0.3.72Compare Source
Patch Changes
93095ee: Make sure node-fetch is version 2.7.0 or greater6bd6fda: DeprecatecreateRouterand its options in favour of the new backend system.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.