What is CVE-2014-5002?

CVE-2014-5002 is a high-severity security vulnerability in lynx (rubygems), affecting versions <= 0.4.0. It is fixed in 1.0.0.

How severe is CVE-2014-5002?

CVE-2014-5002 has a CVSS score of 7.8 (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 lynx are affected by CVE-2014-5002?

lynx (rubygems) versions <= 0.4.0 is affected.

Is there a fix for CVE-2014-5002?

Yes. CVE-2014-5002 is fixed in 1.0.0. Upgrade to this version or later.

Is CVE-2014-5002 exploitable, and should I be worried?

Whether CVE-2014-5002 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-2014-5002 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-2014-5002 in lynx

Q: How severe is CVE-2014-5002?

CVE-2014-5002 has a CVSS score of 7.8 (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 lynx are affected by CVE-2014-5002?

lynx (rubygems) versions <= 0.4.0 is affected.

Q: Is there a fix for CVE-2014-5002?

Yes. CVE-2014-5002 is fixed in 1.0.0. Upgrade to this version or later.

Q: Is CVE-2014-5002 exploitable, and should I be worried?

Whether CVE-2014-5002 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-2014-5002 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-2014-5002?

Upgrade lynx to 1.0.0 or later.

Summary

lynx doesn't properly sanitize user input and exposes database password to unauthorized users

The lynx gem prior to 1.0.0 for Ruby places the configured password on command lines, which allows local users to obtain sensitive information by listing processes.

As of version 1.0.0, lynx no longer supports a --password option. Passwords are only configured in a configuration file, so it's no longer possible to expose passwords on the command line.

Impact

CVE-2014-5002 has a CVSS score of 7.8 (High). The vector is requires local access, 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 (1.0.0); upgrading removes the vulnerable code path.

Affected versions

lynx (<= 0.4.0)

Security releases

lynx → 1.0.0 (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 lynx to 1.0.0 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-2014-5002? CVE-2014-5002 is a high-severity security vulnerability in lynx (rubygems), affecting versions <= 0.4.0. It is fixed in 1.0.0.
How severe is CVE-2014-5002? CVE-2014-5002 has a CVSS score of 7.8 (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 lynx are affected by CVE-2014-5002? lynx (rubygems) versions <= 0.4.0 is affected.
Is there a fix for CVE-2014-5002? Yes. CVE-2014-5002 is fixed in 1.0.0. Upgrade to this version or later.
Is CVE-2014-5002 exploitable, and should I be worried? Whether CVE-2014-5002 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-2014-5002 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-2014-5002? Upgrade lynx to 1.0.0 or later.