GHSA-v34r-vj4r-38j6

### Summary Private maven repository credentials leaked in application logs in case of unsuccessful retrieval operation. ### Details During the execution of an updatecli pipeline which contains a `maven` source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure. Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository .e.g. wrong coordinates provided, not existing artifact or version. ### PoC The [documentation](https://www.updatecli.io/docs/plugins/resource/maven/) currently state to provide user credentials as basic auth inside the `repository` field. e.g. ``` sources: default: kind: maven spec: repository: "{{ requiredEnv "MAVEN_USERNAME" }}:{{ requiredEnv "MAVEN_PASS" }}@repo.example.org/releases" groupid: "org.example.company" artifactid: "my-artifact" versionFilter: kind: regex pattern: "^23(\.[0-9]+){1,2}$" ``` Logs are sanitized properly in case of a successful operation: ``` source: source#default ----------------------------------------------------------- Searching for version matching pattern "^23(\\.[0-9]+){1,2}$" ✔ Latest version is 23.4.0 on the Maven repository at https://repo.example.org/releases/org/example/company/my-artifact/maven-metadata.xml ``` but leaks credentials in case the GAV coordinates are wrong (misspelled package name or missing): ``` source: source#default ----------------------------------------------------------- ERROR: ✗ getting latest version: URL "https://REDACTED:[email protected]/releases/org/example/company/wrong-artifact/maven-metadata.xml" not found or in error ``` ### Impact User credentials/token used to authenticate against a private maven repository can be leaked in clear-text in console or CI logs.