What is CVE-2013-5647?

CVE-2013-5647 is a high-severity code injection vulnerability in sounder (rubygems), affecting versions < 1.0.2. It is fixed in 1.0.2. Untrusted input is evaluated as executable code within the application's runtime environment.

Which versions of sounder are affected by CVE-2013-5647?

sounder (rubygems) versions < 1.0.2 is affected.

Is there a fix for CVE-2013-5647?

Yes. CVE-2013-5647 is fixed in 1.0.2. Upgrade to this version or later.

Is CVE-2013-5647 exploitable, and should I be worried?

Whether CVE-2013-5647 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-2013-5647 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-2013-5647 in sounder

Q: Which versions of sounder are affected by CVE-2013-5647?

sounder (rubygems) versions < 1.0.2 is affected.

Q: Is there a fix for CVE-2013-5647?

Yes. CVE-2013-5647 is fixed in 1.0.2. Upgrade to this version or later.

Q: Is CVE-2013-5647 exploitable, and should I be worried?

Whether CVE-2013-5647 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-2013-5647 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-2013-5647?

Upgrade sounder to 1.0.2 or later.

CVE-2013-5647

CVE-2013-5647 is a high-severity code injection vulnerability in sounder (rubygems), affecting versions < 1.0.2. It is fixed in 1.0.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Sounder Contains Arbitrary Command Execution Vulnerability

lib/sounder/sound.rb in the sounder gem 1.0.1 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a filename.

Impact

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

Affected versions

sounder (< 1.0.2)

Security releases

sounder → 1.0.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 sounder to 1.0.2 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2013-5647? CVE-2013-5647 is a high-severity code injection vulnerability in sounder (rubygems), affecting versions < 1.0.2. It is fixed in 1.0.2. Untrusted input is evaluated as executable code within the application's runtime environment.
Which versions of sounder are affected by CVE-2013-5647? sounder (rubygems) versions < 1.0.2 is affected.
Is there a fix for CVE-2013-5647? Yes. CVE-2013-5647 is fixed in 1.0.2. Upgrade to this version or later.
Is CVE-2013-5647 exploitable, and should I be worried? Whether CVE-2013-5647 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-2013-5647 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-2013-5647? Upgrade sounder to 1.0.2 or later.