What is CVE-2022-23465?

CVE-2022-23465 is a high-severity code injection vulnerability in github.com/migueldeicaza/SwiftTerm (swift), affecting versions < 1.2.0. It is fixed in 1.2.0. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2022-23465?

CVE-2022-23465 has a CVSS score of 7.1 (High). 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/migueldeicaza/SwiftTerm are affected by CVE-2022-23465?

github.com/migueldeicaza/SwiftTerm (swift) versions < 1.2.0 is affected.

Is there a fix for CVE-2022-23465?

Yes. CVE-2022-23465 is fixed in 1.2.0. Upgrade to this version or later.

Is CVE-2022-23465 exploitable, and should I be worried?

Whether CVE-2022-23465 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-2022-23465 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-2022-23465?

Upgrade github.com/migueldeicaza/SwiftTerm to 1.2.0 or later.

CVE-2022-23465 in github.com/migueldeicaza/SwiftTerm

Q: How severe is CVE-2022-23465?

CVE-2022-23465 has a CVSS score of 7.1 (High). 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/migueldeicaza/SwiftTerm are affected by CVE-2022-23465?

github.com/migueldeicaza/SwiftTerm (swift) versions < 1.2.0 is affected.

Q: Is there a fix for CVE-2022-23465?

Yes. CVE-2022-23465 is fixed in 1.2.0. Upgrade to this version or later.

Q: Is CVE-2022-23465 exploitable, and should I be worried?

Whether CVE-2022-23465 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-2022-23465 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-2022-23465?

Upgrade github.com/migueldeicaza/SwiftTerm to 1.2.0 or later.

Summary

SwiftTerm Code Injection vulnerability

Credit

These bugs were found and disclosed by David Leadbeater [email protected] (@dgl at Github.com)

Workarounds

There are no workarounds available

References

Similar exploits to this existed in the past, for terminal emulators:

https://nvd.nist.gov/vuln/detail/CVE-2003-0063
https://nvd.nist.gov/vuln/detail/CVE-2008-2383

Additional background and information is also available:

https://marc.info/?l=bugtraq&m=104612710031920&w=2
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510030

Impact

Attacker could modify the window title via a certain character escape sequence and then insert it back to the command line in the user's terminal, e.g. when the user views a file containing the malicious sequence, which could allow the attacker to execute arbitrary commands.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2022-23465 has a CVSS score of 7.1 (High). The vector is requires local access, no privileges required, and user interaction required. 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 (1.2.0); upgrading removes the vulnerable code path.

Affected versions

github.com/migueldeicaza/SwiftTerm (< 1.2.0)

Security releases

github.com/migueldeicaza/SwiftTerm → 1.2.0 (swift)

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

Fixed in version ce596e0dc8cdb288bc7ed5c6a59011ee3a8dc171

Frequently Asked Questions

What is CVE-2022-23465? CVE-2022-23465 is a high-severity code injection vulnerability in github.com/migueldeicaza/SwiftTerm (swift), affecting versions < 1.2.0. It is fixed in 1.2.0. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2022-23465? CVE-2022-23465 has a CVSS score of 7.1 (High). 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/migueldeicaza/SwiftTerm are affected by CVE-2022-23465? github.com/migueldeicaza/SwiftTerm (swift) versions < 1.2.0 is affected.
Is there a fix for CVE-2022-23465? Yes. CVE-2022-23465 is fixed in 1.2.0. Upgrade to this version or later.
Is CVE-2022-23465 exploitable, and should I be worried? Whether CVE-2022-23465 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-2022-23465 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-2022-23465? Upgrade github.com/migueldeicaza/SwiftTerm to 1.2.0 or later.