What is CVE-2023-32082?

CVE-2023-32082 is a low-severity security vulnerability in github.com/etcd-io/etcd (go), affecting versions < 3.4.26. It is fixed in 3.4.26, 3.5.9.

How severe is CVE-2023-32082?

CVE-2023-32082 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/etcd-io/etcd are affected by CVE-2023-32082?

github.com/etcd-io/etcd (go) versions < 3.4.26 is affected.

Is there a fix for CVE-2023-32082?

Yes. CVE-2023-32082 is fixed in 3.4.26, 3.5.9. Upgrade to this version or later.

Is CVE-2023-32082 exploitable, and should I be worried?

Whether CVE-2023-32082 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-32082 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-32082?

Upgrade: github.com/etcd-io/etcd to 3.4.26 or later, github.com/etcd-io/etcd to 3.5.9 or later.

CVE-2023-32082 in github.com/etcd-io/etcd

Q: How severe is CVE-2023-32082?

CVE-2023-32082 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/etcd-io/etcd are affected by CVE-2023-32082?

github.com/etcd-io/etcd (go) versions < 3.4.26 is affected.

Q: Is there a fix for CVE-2023-32082?

Yes. CVE-2023-32082 is fixed in 3.4.26, 3.5.9. Upgrade to this version or later.

Q: Is CVE-2023-32082 exploitable, and should I be worried?

Whether CVE-2023-32082 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-32082 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-32082?

Upgrade: github.com/etcd-io/etcd to 3.4.26 or later, github.com/etcd-io/etcd to 3.5.9 or later.

Summary

etcd Key name can be accessed via LeaseTimeToLive API

Workarounds

No.

Reporter

Yoni Rozenshein

Impact

LeaseTimeToLive API allows access to key names (not value) associated to a lease when Keys parameter is true, even a user doesn't have read permission to the keys. The impact is limited to a cluster which enables auth (RBAC).

CVE-2023-32082 has a CVSS score of 3.1 (Low). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.4.26, 3.5.9); upgrading removes the vulnerable code path.

Affected versions

github.com/etcd-io/etcd (< 3.4.26) github.com/etcd-io/etcd (>= 3.5.0, < 3.5.9)

Security releases

github.com/etcd-io/etcd → 3.4.26 (go) github.com/etcd-io/etcd → 3.5.9 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

< v3.4.26 and < v3.5.9 are affected.

Frequently Asked Questions

What is CVE-2023-32082? CVE-2023-32082 is a low-severity security vulnerability in github.com/etcd-io/etcd (go), affecting versions < 3.4.26. It is fixed in 3.4.26, 3.5.9.
How severe is CVE-2023-32082? CVE-2023-32082 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/etcd-io/etcd are affected by CVE-2023-32082? github.com/etcd-io/etcd (go) versions < 3.4.26 is affected.
Is there a fix for CVE-2023-32082? Yes. CVE-2023-32082 is fixed in 3.4.26, 3.5.9. Upgrade to this version or later.
Is CVE-2023-32082 exploitable, and should I be worried? Whether CVE-2023-32082 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-32082 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-32082?
- Upgrade github.com/etcd-io/etcd to 3.4.26 or later
- Upgrade github.com/etcd-io/etcd to 3.5.9 or later

Other vulnerabilities in github.com/etcd-io/etcd

CVE-IDSeverityPackage summary

CVE-2020-15113Mediumgithub.com/etcd-io/etcd: Improper Preservation of Permissions in etcd