Home / CVE DB / CVE-2017-5659
Standard
Vulnerability Identifier

CVE-2017-5659

2017-04-17
Severity Assessment
LOW
CVSS v3.x Score
Clinical Analysis (Description)

Apache Traffic Server before 6.2.1 generates a coredump when there is a mismatch between content length and chunked encoding.

Vector Sequencing

Attack Parameters

Impact Consequences

Technical Impact

CVSS v2 Score (Legacy)
5.0

For backward compatibility

EPSS Probability
1.97%

Percentile: 83.6%

Weakness Classification

CWE-CWE-20

Affected Population

Affected Configurations

Total: 60 detected entries

Software List Scrollable
ap
traffic_server
Vendor: apache • v5.0.1
ap
traffic_server
Vendor: apache • v5.2.0
ap
traffic_server
Vendor: apache • v2.1.9
ap
traffic_server
Vendor: apache • v2.1.5
ap
traffic_server
Vendor: apache • v4.2.0
ap
traffic_server
Vendor: apache • v3.1.2
ap
traffic_server
Vendor: apache • v3.2.4
ap
traffic_server
Vendor: apache • v6.0.0
ap
traffic_server
Vendor: apache • v2.1.7
ap
traffic_server
Vendor: apache • v6.0.3
ap
traffic_server
Vendor: apache • v5.1.1
ap
traffic_server
Vendor: apache • v2.0.1
ap
traffic_server
Vendor: apache • v4.0.0
ap
traffic_server
Vendor: apache • v2.1.1
ap
traffic_server
Vendor: apache • v3.0.1
ap
traffic_server
Vendor: apache • v3.3.4
ap
traffic_server
Vendor: apache • v5.2.1
ap
traffic_server
Vendor: apache • v6.2.0
ap
traffic_server
Vendor: apache • v5.3.0
ap
traffic_server
Vendor: apache • v5.3.1
ap
traffic_server
Vendor: apache • v2.1.6
ap
traffic_server
Vendor: apache • v4.2.2
ap
traffic_server
Vendor: apache • v5.3.2
ap
traffic_server
Vendor: apache • v3.0.0
ap
traffic_server
Vendor: apache • v5.0.0
ap
traffic_server
Vendor: apache • v2.1.8
ap
traffic_server
Vendor: apache • v2.1.4
ap
traffic_server
Vendor: apache • v6.1.0
ap
traffic_server
Vendor: apache • v3.2.2
ap
traffic_server
Vendor: apache • v3.3.5
ap
traffic_server
Vendor: apache • v2.1.2
ap
traffic_server
Vendor: apache • v5.1.2
ap
traffic_server
Vendor: apache • v3.0.4
ap
traffic_server
Vendor: apache • v2.1.3
ap
traffic_server
Vendor: apache • v3.1.3
ap
traffic_server
Vendor: apache • v3.1.1
ap
traffic_server
Vendor: apache • v3.2.5
ap
traffic_server
Vendor: apache • v4.1.0
ap
traffic_server
Vendor: apache • v3.0.2
ap
traffic_server
Vendor: apache • v2.0.0
ap
traffic_server
Vendor: apache • v4.1.1
ap
traffic_server
Vendor: apache • v3.2.0
ap
traffic_server
Vendor: apache • v3.1.4
ap
traffic_server
Vendor: apache • v3.3.1
ap
traffic_server
Vendor: apache • v3.3.0
ap
traffic_server
Vendor: apache • v5.1.0
ap
traffic_server
Vendor: apache • v4.2.3
ap
traffic_server
Vendor: apache • v3.1.0
ap
traffic_server
Vendor: apache • v3.3.2
ap
traffic_server
Vendor: apache • v3.2.1
ap
traffic_server
Vendor: apache • v3.0.3
ap
traffic_server
Vendor: apache • v6.1.1
ap
traffic_server
Vendor: apache • v4.2.1
ap
traffic_server
Vendor: apache • v2.1.0
ap
traffic_server
Vendor: apache • v4.0.2
ap
traffic_server
Vendor: apache • v4.2.1.1
ap
traffic_server
Vendor: apache • v3.3.3
ap
traffic_server
Vendor: apache • v4.0.1
ap
traffic_server
Vendor: apache • v3.0.5
ap
traffic_server
Vendor: apache • v4.1.2
Timeline

Time Line

PUBLICATION
17 Apr 2017
MODIFICATION
20 Apr 2025
Impact Statistics

Key Metrics

CVSS Score
LOW
Products
60
Affected
Remediation Protocol

Recommended Solution

No automatic solution found. Check vendor references.
Patch Library
No direct patch listed in database.
Recommended Actions for Administrators

Immediate Action Plan

1. Inventory

Identify all affected systems in your infrastructure.

2. Assessment

Assess exposure and criticality for your organization.

3. Mitigation

Apply patches or available workarounds.

4. Verification

Test and confirm effectiveness of applied measures.