CVE-2025-68121 detected on CustomScriptExtension 2.1.19 on AzureLinux V3

Open
#262 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
azure, go

Research direction

Start with the two CustomScriptExtension 2.1.19 binaries listed in the issue and compare their Go dependency information with the CVE record. Read PRs #256 and #245 alongside the CVE details to determine whether the reported crypto/tls vulnerability applies. Done means the impact is confirmed or ruled out and the issue records the required remediation or justification.

Written by the indexing model from the issue text.

Description

CRI 21000001809436

security scanning tool (Orca) identified CVE-2025-68121 on AKS nodes. The vulnerability was detected in the following binaries:

/var/lib/waagent/Microsoft.Azure.Extensions.CustomScript-2.1.19/bin/custom-script-extension
/var/lib/waagent/Microsoft.Azure.Extensions.CustomScript-2.1.19/bin/custom-script-extension-arm64

CVE Record: CVE-2025-68121

CSE 2.1.19 seems to be there CSE 2.1.19 by norakoiralamsft · Pull Request #256 · Azure/custom-script-extension-linux

And it seems to have golang.org/x/crypto version v0.45.0
golang.org/x/crypto version update by norakoiralamsft · Pull Request #245 · Azure/custom-script-extension-linux

So I'm not sure of the CVE Record: CVE-2025-68121 which says :

Vendor = Go standard library

Product = crypto/tls

Versions 3 Total

Default Status: unaffected

affected

affectedfrom 0before 1.24.13

affectedfrom 1.25.0-0before 1.25.7

affectedfrom 1.26.0-rc.1before 1.26.0-rc.3

Dominant language
Go
Stars
113
Forks
46
Avg merge
4d 15h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/custom-script-extension-linux

All issues in Azure/custom-script-extension-linux

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.