Menu

Star on GitHub · 3.2k

CVE-2014-0349

10.0 · HIGH

Multiple unspecified vulnerabilities in J2k-Codec allow remote attackers to execute arbitrary code via a crafted JPEG 2000 file.

Published Apr 12, 2014j2k-codecEPSS 3.80%

Overview

CVE-2014-0349 is a high-severity vulnerability affecting j2k-codec j2k-codec. It was published on April 12, 2014 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Multiple unspecified vulnerabilities in J2k-Codec allow remote attackers to execute arbitrary code via a crafted JPEG 2000 file.

Remediation

Check the references section for vendor advisories and patches from j2k-codec. Update j2k-codec to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2014-0349?

CVE-2014-0349 is a high-severity vulnerability affecting j2k-codec j2k-codec. It was published on April 12, 2014 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2014-0349?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2014-0349?

Check the references section for vendor advisories and patches from j2k-codec. Update j2k-codec to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2014-0349?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2014-0349 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2014

View all