Skip to content
Noroxi
CVE-2013-4623· NVD / CVE Program· CNA mitre

The x509parse_crt function in x509.h in PolarSSL 1.1.x before 1.1.7 and 1.2.x before 1.2.8 does not properly parse certificate messages duri

The x509parse_crt function in x509.h in PolarSSL 1.1.x before 1.1.7 and 1.2.x before 1.2.8 does not properly parse certificate messages during the SSL/TLS handshake, which allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a certificate message that contains a PEM encoded certificate.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Sep 30, 2013
Updated
Jun 16, 2026
EPSS
1.9% · 79th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.9%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
polarsslpolarssl

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • polarssl polarssl1.1.0
  • polarssl polarssl1.1.1
  • polarssl polarssl1.1.2
  • polarssl polarssl1.1.3
  • polarssl polarssl1.1.4
  • polarssl polarssl1.1.5
  • polarssl polarssl1.1.6
  • polarssl polarssl1.2.0
  • polarssl polarssl1.2.1
  • polarssl polarssl1.2.2
  • polarssl polarssl1.2.3
  • polarssl polarssl1.2.4
  • polarssl polarssl1.2.5
  • polarssl polarssl1.2.6
  • polarssl polarssl1.2.7

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:6.0polarsslbefore 1.2.9-1~deb6u11.2.9-1~deb6u1
Debian:7polarsslbefore 1.2.9-1~deb7u11.2.9-1~deb7u1

Other highest-scoring records for the same primary product.

  • CVE-2011-4574PolarSSL versions prior to v1.1 use the HAVEGE random number generation algorithm.
    39Monitor
  • CVE-2014-9744Memory leak in PolarSSL before 1.3.9 allows remote attackers to cause a denial of service (memory consumption) via a large number of ClientH
    32Monitor
  • CVE-2014-8628Memory leak in PolarSSL before 1.2.12 and 1.3.x before 1.3.9 allows remote attackers to cause a denial of service (memory consumption) via a
    32Monitor
  • CVE-2015-1182The asn1_get_sequence_of function in library/asn1parse.c in PolarSSL 1.0 through 1.2.12 and 1.3.x through 1.3.9 does not properly initialize
    31Monitor
  • CVE-2012-2130A Security Bypass vulnerability exists in PolarSSL 0.99pre4 through 1.1.1 due to a weak encryption error when generating Diffie-Hellman valu
    30Monitor
  • CVE-2015-8036Heap-based buffer overflow in ARM mbed TLS (formerly PolarSSL) 1.3.x before 1.3.14 and 2.x before 2.1.2 allows remote SSL servers to cause a
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:polarssl1.2.9-1~deb6u1 · Debian:6.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records