fix(deps): update dependency @backstage/plugin-app-backend to v0.3.75 [security] #294
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.57
->0.3.75
GitHub 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.75
of the@backstage/plugin-app-backend
package. 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
Release Notes
backstage/backstage (@backstage/plugin-app-backend)
v0.3.75
Compare Source
Patch Changes
094eaa3
: Remove references to in-repo backend-commonv0.3.74
Compare 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-app
package590fb2d
: BREAKING: The app backend now supports the newindex.html.tmpl
output from@backstage/cli
. If available, theindex.html
will 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.baseUrl
to the app backend plugin at runtime.An effect that this change has is that the
index.html
will 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.disableConfigInjection
configuration option totrue
.d425fc4
: Modules, plugins, and services are nowBackendFeature
, not a function that returns a feature.c2b63ab
: Updated dependencysupertest
to^7.0.0
.Updated dependencies
v0.3.73
Compare Source
v0.3.72
Compare Source
Patch Changes
93095ee
: Make sure node-fetch is version 2.7.0 or greater6bd6fda
: DeprecatecreateRouter
and its options in favour of the new backend system.v0.3.71
Compare Source
Patch Changes
v0.3.70
Compare Source
Patch Changes
v0.3.69
Compare Source
v0.3.68
Compare Source
Patch Changes
8869b8e
: Updated local development setup.78a0b08
: Internal refactor to handleBackendFeature
contract change.82c2b90
: Restore the support of external config schema in the router of theapp-backend
plugin, which was broken in release1.26.0
.This support is critical for dynamic frontend plugins to have access to their config values.
d44a20a
: Added additional plugin metadata topackage.json
.v0.3.67
Compare Source
v0.3.66
Compare Source
Patch Changes
d229dc4
: Move path utilities frombackend-common
to thebackend-plugin-api
package.v0.3.65
Compare Source
Patch Changes
d5a1fe1
: Replaced winston logger withLoggerService
c884b9a
: Track assets namespace in the cache store, implement a cookie authentication for when the public entry is enabled and used with the new auth services.v0.3.64
Compare Source
Patch Changes
v0.3.63
Compare Source
Patch Changes
v0.3.62
Compare Source
Patch Changes
52e43f2
: Disable default auth policy, allowing unauthenticated access to app bundle.v0.3.61
Compare Source
Patch Changes
v0.3.60
Compare Source
v0.3.59
Compare Source
v0.3.58
Compare Source
Patch Changes
9aac2b0
: Use--cwd
as the firstyarn
argument998ccf6
: Support injecting config multiple times in a single bundle6bb6f3e
: Updated dependencyfs-extra
to^11.2.0
.Updated dependency
@types/fs-extra
to^11.0.0
.54ad8e1
: Allow theapp-backend
plugin to use a global configuration schema provided externally through an extension.9dfd57d
: Do not force caching of the Javascript asset that contains the injected config.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.