What is CVE-2013-7377?

CVE-2013-7377 is a high-severity command injection vulnerability in codem-transcode (npm), affecting versions < 0.5.0. It is fixed in 0.5.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

How severe is CVE-2013-7377?

CVE-2013-7377 has a CVSS score of 8.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 codem-transcode are affected by CVE-2013-7377?

codem-transcode (npm) versions < 0.5.0 is affected.

Is there a fix for CVE-2013-7377?

Yes. CVE-2013-7377 is fixed in 0.5.0. Upgrade to this version or later.

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

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

Upgrade codem-transcode to 0.5.0 or later.

CVE-2013-7377 in codem-transcode

Q: How severe is CVE-2013-7377?

CVE-2013-7377 has a CVSS score of 8.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 codem-transcode are affected by CVE-2013-7377?

codem-transcode (npm) versions < 0.5.0 is affected.

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

Yes. CVE-2013-7377 is fixed in 0.5.0. Upgrade to this version or later.

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

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

Upgrade codem-transcode to 0.5.0 or later.

Summary

Potential Command Injection in codem-transcode

When the ffprobe functionality is enabled on the server, HTTP POST requests can be made to /probe. These requests are passed to the ffprobe binary on the server. Through this HTTP endpoint it is possible to send a malformed source file name to ffprobe that results in arbitrary command execution.

Mitigating Factors:

The ffprobe functionality is not enabled by default. In addition, exploitation opportunities are limited in a standard configuration because the server binds to the local interface by default.

Impact

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2013-7377 has a CVSS score of 8.1 (High). The vector is network-reachable, no 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 (0.5.0); upgrading removes the vulnerable code path.

Affected versions

codem-transcode (< 0.5.0)

Security releases

codem-transcode → 0.5.0 (npm)

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

An updated and patched version of the module (version 0.5.0) is available via npm. Users who have enabled the ffprobe functionality are especially encouraged to upgrade..

Frequently Asked Questions

What is CVE-2013-7377? CVE-2013-7377 is a high-severity command injection vulnerability in codem-transcode (npm), affecting versions < 0.5.0. It is fixed in 0.5.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
How severe is CVE-2013-7377? CVE-2013-7377 has a CVSS score of 8.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 codem-transcode are affected by CVE-2013-7377? codem-transcode (npm) versions < 0.5.0 is affected.
Is there a fix for CVE-2013-7377? Yes. CVE-2013-7377 is fixed in 0.5.0. Upgrade to this version or later.
Is CVE-2013-7377 exploitable, and should I be worried? Whether CVE-2013-7377 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-7377 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-7377? Upgrade codem-transcode to 0.5.0 or later.