Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Illustration for: Portainer fixes Git credential leak to read-only users in 2.45.4 and 2.39.9

    Portainer fixes Git credential leak to read-only users in 2.45.4 and 2.39.9

    Portainer

    Portainer lets read-only users redirect stored Git credentials

    A signed-in Portainer user with read access to a shared Git source that holds credentials can make Portainer send that source's stored username and password, or token, to a host of the user's choosing. Read-only users are normally not supposed to see that secret.

    Git's HTTP transport sends Basic credentials on its first request without waiting for a challenge, so the attacker's server receives them in plaintext. What the stolen credential unlocks depends on the scope its owner gave it on the Git provider, and in GitOps setups those repositories feed what Portainer deploys.

    The advisory gives no CVSS score, and no CVE id is listed for the flaw.

    Connection tests and repository browsing both trust the request's URL

    Portainer can save repository credentials with Git sources, Git-backed stacks, edge stacks and custom templates, and it offers a connection test and a repository browser for them. The connection test for a saved GitOps source accepts a repository URL supplied with each request, yet still authenticates with the source's saved credentials. It needs only read access to the source.

    In Business Edition, the browsing endpoints (listing references, searching files, previewing a file, reading Helm values) take the secret from the stack, edge stack or template you reference but contact whatever repository URL the request names. Either way, one authenticated network request is enough, with no user interaction and low privileges.

    Portainer 2.39 LTS through 2.45 and some STS lines exposed

    The connection-test flaw is said to have arrived with GitOps sources in 2.43.0 and affects both Community and Business Edition. The repository browsing flaw affects Business Edition, including the 2.39 LTS line.

    The advisory's table marks 2.45.x (both editions) as vulnerable from 2.45.0 and 2.39.x (Business Edition only) from 2.39.0. Versions 2.40.x through 2.44.x are also affected: 2.43.x and 2.44.x in both editions, earlier lines in Business Edition only. These short-term lines get no dedicated patch.

    The advisory does not say whether anyone has exploited the flaw in the wild, so treat the exploitation status as unknown.

    Update to 2.45.4, 2.39.9 or 3.0.0 or later

    On the 2.45.x LTS branch, update to 2.45.4. On the 2.39.x LTS branch (Business Edition), update to 2.39.9. Portainer 3.0.0 and later already contain the fix, and the advisory tells users on the short-term lines to move to 2.45.4 or 3.1.0. Releases before 2.39.0 are end-of-life and will not be fixed, so those users need to move to a supported LTS branch.

    If you cannot update yet, the advisory offers these mitigations:

    • Limit sharing of Git sources that hold stored credentials to administrators or the source's owner.
    • In Business Edition, restrict who can see Git-backed stacks and custom templates with stored credentials.
    • Where credentials are required, use a read-only token restricted to the specific repository.

    If untrusted users could read credentialed sources, stacks or templates, rotate those tokens and review the Git provider's access logs for use from unexpected addresses. A separate advisory, GHSA-45qw-5wc8-pw8v, covers a cached ECR registry token returned to standard users and is fixed in the same 2.39.9 and 2.45.4 releases.

    What the Portainer advisory leaves unsaid

    The advisory gives no publication or patch release date. It names no reporter or discoverer. It also does not say which Git providers or credential types are at risk beyond the stored username and password or token.

    Product Affected Fixed
    Portainer 2.45.x LTS (Community and Business Edition) 2.45.0 and later in the branch, before the fix 2.45.4
    Portainer 2.39.x LTS (Business Edition) 2.39.0 and later in the branch, before the fix 2.39.9
    Portainer 2.40.x through 2.44.x (STS) 2.40.x through 2.44.x, no dedicated patch 2.45.4 or 3.1.0

    Sources

    Image: “Lock and Key | 1700–1730” by museado, CC0 1.0, via flickr (Openverse)


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion