What is CVE-2020-13353?

CVE-2020-13353 is a low-severity security vulnerability in gitaly (rubygems), affecting versions >= 1.79.0, < 13.3.9. It is fixed in 13.3.9, 13.4.5, 13.5.2.

How severe is CVE-2020-13353?

CVE-2020-13353 has a CVSS score of 3.2 (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 gitaly are affected by CVE-2020-13353?

gitaly (rubygems) versions >= 1.79.0, < 13.3.9 is affected.

Is there a fix for CVE-2020-13353?

Yes. CVE-2020-13353 is fixed in 13.3.9, 13.4.5, 13.5.2. Upgrade to this version or later.

Is CVE-2020-13353 exploitable, and should I be worried?

Whether CVE-2020-13353 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-2020-13353 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.

CVE-2020-13353 in gitaly

Q: How severe is CVE-2020-13353?

CVE-2020-13353 has a CVSS score of 3.2 (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 gitaly are affected by CVE-2020-13353?

gitaly (rubygems) versions >= 1.79.0, < 13.3.9 is affected.

Q: Is there a fix for CVE-2020-13353?

Yes. CVE-2020-13353 is fixed in 13.3.9, 13.4.5, 13.5.2. Upgrade to this version or later.

Q: Is CVE-2020-13353 exploitable, and should I be worried?

Whether CVE-2020-13353 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-2020-13353 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-2020-13353?

Upgrade: gitaly to 13.3.9 or later, gitaly to 13.4.5 or later, gitaly to 13.5.2 or later.

Summary

Gitaly Insufficient Session Expiration vulnerability

When importing repos via URL, one time use git credentials were persisted beyond the expected time window in Gitaly 1.79.0 or above. Affected versions are: >=1.79.0, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.

Impact

CVE-2020-13353 has a CVSS score of 3.2 (Low). The vector is requires local access, high 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 (13.3.9, 13.4.5, 13.5.2); upgrading removes the vulnerable code path.

Affected versions

gitaly (>= 1.79.0, < 13.3.9) gitaly (>= 13.4, < 13.4.5) gitaly (>= 13.5, < 13.5.2)

Security releases

gitaly → 13.3.9 (rubygems) gitaly → 13.4.5 (rubygems) gitaly → 13.5.2 (rubygems)

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

Upgrade the following packages to resolve this vulnerability:

gitaly to 13.3.9 or later; gitaly to 13.4.5 or later; gitaly to 13.5.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2020-13353? CVE-2020-13353 is a low-severity security vulnerability in gitaly (rubygems), affecting versions >= 1.79.0, < 13.3.9. It is fixed in 13.3.9, 13.4.5, 13.5.2.
How severe is CVE-2020-13353? CVE-2020-13353 has a CVSS score of 3.2 (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 gitaly are affected by CVE-2020-13353? gitaly (rubygems) versions >= 1.79.0, < 13.3.9 is affected.
Is there a fix for CVE-2020-13353? Yes. CVE-2020-13353 is fixed in 13.3.9, 13.4.5, 13.5.2. Upgrade to this version or later.
Is CVE-2020-13353 exploitable, and should I be worried? Whether CVE-2020-13353 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-2020-13353 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-2020-13353?
- Upgrade gitaly to 13.3.9 or later
- Upgrade gitaly to 13.4.5 or later
- Upgrade gitaly to 13.5.2 or later