David Fiser

O software apresenta uma vulnerabilidade de bypass de autenticação decorrente de atribuições incorretas de permissão em um token de conta de armazenamento. Isso permite que atacantes remotos contornem a autenticação sem a necessidade de realizar login. A falha possibilita que atacantes acessem o sistema explorando as permissões associadas ao token. Vários relatórios indicam o potencial para riscos na cadeia de suprimentos, incluindo a capacidade de substituir modelos de IA. Não foram relatados números estimados de dispositivos afetados ou incidentes no mundo real além da descoberta da falha.

O software contém um bypass de autenticação devido à atribuição incorreta de permissões de tokens SAS. Isso permite acesso não autorizado.

Nome do Software Vulnerável e Versões Afetadas: NVIDIA Riva (versões afetadas não especificadas) Descrição: O problema está relacionado a controle de acesso inadequado, que poderia ser explorado para causar adulteração de dados ou negação de serviço. Recomendações: Até o momento, não há informações sobre uma versão mais recente que contenha uma correção para esta vulnerabilidade.

The issue is related to improper access control, which could lead to escalation of privileges, data tampering, denial of service, or information disclosure. A successful exploit of this vulnerability might have significant consequences. The estimated number of potentially affected devices worldwide is not specified. There are reports of real-world incidents where this issue was exploited.

O problema está relacionado ao Azure Service Fabric Container e envolve uma vulnerabilidade de elevação de privilégios. Essa vulnerabilidade está associada ao daemon WAagent e ao seu gerenciamento inseguro de privilégios. A exploração desse problema poderia permitir que um invasor elevasse seus privilégios.

The issue allows stored credentials to be stored unencrypted in job config.xml files on the Jenkins master. These credentials could be viewed by users with Extended Read permission or access to the master file system.

The issue concerns the storage of credentials in an unencrypted manner within the global configuration file and job config.xml files on the Jenkins master. This allows users with Extended Read permission or access to the master file system to view these credentials.

The issue concerns the storage of sensitive information by the Jenkins Sofy.AI Plugin. Specifically, it stores credentials and an API token unencrypted in job config.xml files on the Jenkins master or controller. This unencrypted storage allows users with Extended Read permission or access to the master or controller file system to view these sensitive details. There is no information provided about the estimated number of potentially affected devices or real-world incidents related to this issue.

The issue concerns the storage of credentials in an unencrypted manner within job config.xml files on the Jenkins master. Users with Extended Read permission or access to the master file system can view these credentials.

The issue concerns the storage of credentials in an unencrypted manner within job config.xml files on the Jenkins master or controller. These credentials can be accessed by users who have Extended Read permission or those with direct access to the master or controller file system.

The issue concerns the storage of credentials in an unencrypted manner within the global config.xml configuration file on the Jenkins master. This allows users with access to the master file system to view these credentials.

The issue concerns the storage of credentials in an unencrypted manner within the global configuration file on the Jenkins master or controller. Specifically, the credentials are stored in the `com.soasta.jenkins.CloudTestServer.xml` file. This could allow users with access to the Jenkins controller file system to view these credentials. There is no information provided about the estimated number of potentially affected devices or real-world incidents where this issue was exploited.

The issue concerns the storage of sensitive information in an unencrypted manner. Specifically, the Jenkins View26 Test-Reporting Plugin stores credentials and an access token unencrypted in job config.xml files on the Jenkins master or controller. This allows users with Extended Read permission or access to the master or controller file system to view these sensitive details.

The issue concerns the storage of credentials in an unencrypted manner within the global configuration file of the Jenkins master. This allows users with access to the master file system to view these credentials.

The issue concerns the storage of credentials in an unencrypted manner in job config.xml files on the Jenkins master. These credentials can be accessed by users with Extended Read permission or those who have access to the master file system.

The issue concerns the storage of credentials in an unencrypted manner within the global configuration file on the Jenkins master. This allows users with access to the master file system to view these credentials.

The issue concerns the storage of credentials in an unencrypted manner within the global configuration file on the Jenkins master or controller. Specifically, the credentials are stored in the hudson.plugins.testlink.TestLinkBuilder.xml file. This allows users with access to the Jenkins controller or master file system to view these credentials. There is no information available about the estimated number of potentially affected devices or real-world incidents where this issue was exploited.

The issue allows credentials to be stored unencrypted in job config.xml files on the Jenkins master. These credentials can be viewed by users with Extended Read permission or those who have access to the master file system.

A stored cross-site scripting issue allows attackers who can edit descriptions and other fields to insert links with the `javascript:` scheme into the Jenkins UI. The PegDown Formatter Plugin uses the PegDown library to render Markdown formatted descriptions and advertises disabling of HTML to prevent cross-site scripting, but it does not prevent the use of the `javascript:` scheme in URLs for links. This results in an exploitable issue by users able to configure entities with descriptions that are rendered by the configured markup formatter.

The issue allows attackers who can configure jobs in Jenkins to read the contents of any file on the Jenkins master. This is due to an arbitrary file read vulnerability.