CVE-2024-47762

Backstage is an open framework for building developer portals. Configuration supplied through APP_CONFIG_* environment variables, for example APP_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 the APP_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. The issue has been resolved in version 0.3.75 of the @backstage/plugin-app-backend package. 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.

CVSS v3 5.8 MEDIUM

5.8^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 3.9 / Impact : 1.4

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact LOW

Integrity Impact NONE

Availability Impact NONE

Scope CHANGED

References

Link	Resource
https://github.com/backstage/backstage/commit/323e6129073c5cb4cc106a1239eaec31a129554f
https://github.com/backstage/backstage/security/advisories/GHSA-qc4v-xq2m-65wc

Configurations

No configuration.

History

No history.

Information

Published : 2024-10-03 18:15

Updated : 2024-10-04 13:50

NVD link : CVE-2024-47762

Mitre link : CVE-2024-47762

CVE.ORG link : CVE-2024-47762

JSON object : View

Products Affected

No product.

CWE

CWE-440

Expected Behavior Violation

{"id": "CVE-2024-47762", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 5.8, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2024-10-03T18:15:05.287", "references": [{"url": "https://github.com/backstage/backstage/commit/323e6129073c5cb4cc106a1239eaec31a129554f", "source": "security-advisories@github.com"}, {"url": "https://github.com/backstage/backstage/security/advisories/GHSA-qc4v-xq2m-65wc", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-440"}]}], "descriptions": [{"lang": "en", "value": "Backstage is an open framework for building developer portals. Configuration supplied through APP_CONFIG_* environment variables, for example APP_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 the APP_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. The issue has been resolved in version 0.3.75 of the @backstage/plugin-app-backend package. 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."}, {"lang": "es", "value": "Backstage es un framework abierto para crear portales para desarrolladores. La configuraci\u00f3n suministrada a trav\u00e9s de las variables de entorno APP_CONFIG_*, por ejemplo APP_CONFIG_backend_listen_port=7007, ignoraba inesperadamente la visibilidad definida en el esquema de configuraci\u00f3n. Esto ocurr\u00eda incluso si el esquema de configuraci\u00f3n especificaba que deb\u00edan tener visibilidad secreta o de backend. Esta era una caracter\u00edstica prevista de la forma APP_CONFIG_* de suministrar configuraci\u00f3n, pero ahora claramente va en contra del comportamiento esperado del sistema de configuraci\u00f3n. Este comportamiento conlleva un riesgo de exponer potencialmente detalles de configuraci\u00f3n confidenciales que se pretende que permanezcan privados o restringidos a los procesos de backend. El problema se ha resuelto en la versi\u00f3n 0.3.75 del paquete @backstage/plugin-app-backend. Como medida temporal, evite suministrar secretos mediante el patr\u00f3n de configuraci\u00f3n APP_CONFIG_. Considere m\u00e9todos alternativos para configurar secretos, como la sustituci\u00f3n de entorno disponible para la configuraci\u00f3n de Backstage."}], "lastModified": "2024-10-04T13:50:43.727", "sourceIdentifier": "security-advisories@github.com"}