Security readout for executives and security teams
Plain-English summary
CVE-2018-6347 is a denial-of-service flaw in Facebook Proxygen's HTTP/2 header and trailer parsing. A remote, unauthenticated attacker could cause service availability impact. The CVE rates it high because exploitation is network reachable, low complexity, and affects availability, not data confidentiality or integrity.
Executive priority
Prioritize remediation for public or business-critical Proxygen-backed services because the risk is service disruption. Data theft is not indicated by the CVE, but downtime can still affect customers and operations.
Technical view
Proxygen versions before v2018.12.31.00 mishandle HTTP/2 parsing of headers or trailers, mapped to CWE-400 resource management. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. The supplied sources identify a related upstream commit but do not provide detailed exploit conditions.
Likely exposure
Exposure is likely limited to services directly using Facebook Proxygen before v2018.12.31.00, especially where HTTP/2 traffic reaches the Proxygen component over the network.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. Treat exploitation status as unconfirmed while prioritizing internet-facing or high-availability Proxygen deployments.
Researcher notes
Evidence is concise: CVE description, CVSS, CWE-400, affected version boundary, and one GitHub commit. No source in the bundle confirms active exploitation, broad product embedding, or detailed mitigations beyond updating past the affected range.
Mitigation direction
- Upgrade Proxygen to v2018.12.31.00 or later.
- Review the referenced upstream commit and vendor guidance.
- Prioritize internet-facing HTTP/2 Proxygen services.
- Apply availability monitoring during rollout.
- Document any compensating controls if upgrade is delayed.
Validation and detection
- Inventory services and dependencies using Facebook Proxygen.
- Confirm deployed Proxygen versions are not before v2018.12.31.00.
- Identify whether HTTP/2 reaches Proxygen in production paths.
- Review logs and monitoring for unexplained availability degradation.
- Track remediation evidence in vulnerability management records.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2018-6347 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/facebook/proxygen/commit/223e0aa6bc7590e86af1e917185a2e0efe160711CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.