How severe is GHSA-v34r-vj4r-38j6?

GHSA-v34r-vj4r-38j6 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-v34r-vj4r-38j6?

GHSA-v34r-vj4r-38j6 affects the following packages: github.com/updatecli/updatecli (Go). Ecosystems affected: Go.

How do I fix GHSA-v34r-vj4r-38j6?

Update github.com/updatecli/updatecli to 0.93.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v34r-vj4r-38j6 is resolved across your whole dependency graph.

How do I detect GHSA-v34r-vj4r-38j6 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/updatecli/updatecli. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v34r-vj4r-38j6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v34r-vj4r-38j6?

O3 pinpoints whether GHSA-v34r-vj4r-38j6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v34r-vj4r-38j6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v34r-vj4r-38j6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v34r-vj4r-38j6?

GHSA-v34r-vj4r-38j6 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v34r-vj4r-38j6?

GHSA-v34r-vj4r-38j6 is classified as CWE-359 (CWE-359). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v34r-vj4r-38j6 published, and has it been updated?

GHSA-v34r-vj4r-38j6 was published on January 24, 2025 and was last updated on January 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-v34r-vj4r-38j6

HIGH

Updatecli exposes Maven credentials in console output

Also known asCVE-2025-24355GO-2025-3419

Published

Jan 24, 2025

Updated

Jan 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk13th percentile+0.17%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/updatecli/updatecli

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/updatecli/updatecli`	all versions	0.93.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/updatecli/updatecli. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/updatecli/updatecli to 0.93.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v34r-vj4r-38j6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v34r-vj4r-38j6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v34r-vj4r-38j6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.upda

O3 Security · Impact-Aware SCA

Is GHSA-v34r-vj4r-38j6 in your dependencies?

O3 detects GHSA-v34r-vj4r-38j6 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works