Security readout for executives and security teams
Plain-English summary
This issue can let unauthenticated remote users make a FlightPHP application consume excessive memory by sending large request bodies. The likely business impact is service outage, not data theft. The source bundle says the flaw was fixed in v1.2 by changing request body loading behavior.
Executive priority
High priority for internet-facing services because the impact is outage and the fix is a framework upgrade. It should be handled in the next normal security maintenance window, faster for critical public applications.
Technical view
Before v1.2, mikecao/flight eagerly read the entire HTTP request body in the Request constructor for every request. Large payloads could exhaust memory and crash or degrade the application. The CVSS vector is network, low complexity, no privileges, no user interaction, with high availability impact only.
Likely exposure
Exposure is most likely in applications using mikecao/flight before v1.2, especially public routes that receive HTTP requests with bodies. The affected entry specifically names package mikecao/flight, product core, version v1.0, with the description stating versions prior to v1.2.
Exploitation context
The source bundle references a public proof-of-concept repository, but KEV is false and no cited source confirms active exploitation. Treat exploitation as plausible for exposed applications because the weakness is remote, unauthenticated, and low complexity.
Researcher notes
Evidence supports CWE-770 and availability-only impact. The public references include the fixing pull request, commit, and a proof-of-concept repository. Do not infer confidentiality or integrity compromise from the supplied sources.
Mitigation direction
- Upgrade mikecao/flight to v1.2 or later where this framework is used.
- Prioritize internet-facing FlightPHP applications that accept request bodies.
- Check FlightPHP vendor guidance before relying on temporary compensating controls.
- Monitor memory exhaustion, worker crashes, and availability errors during remediation.
Validation and detection
- Inventory Composer dependencies for mikecao/flight and identify versions below v1.2.
- Map public routes served by affected FlightPHP applications.
- Confirm deployed code includes the lazy request-body loading fix from v1.2.
- Review logs and metrics for memory spikes or repeated request-related crashes.
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-770: 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-2014-125127 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
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.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.