Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
PRODUCT FAMILYFRAMEWORKPARTIAL

Phoenix Framework Project

Phoenix Framework

Phoenix Framework is tracked by BlackTree as a software framework or development platform. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Lifecycle status

No support or retirement date is shown unless BlackTree can link it to a registered publisher source. A missing date means that a boundary is not publicly stated, has not yet been extracted, or still needs source routing. It does not mean the product is supported indefinitely.

Product overview

Phoenix Framework is tracked by BlackTree as a software framework or development platform. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Main capabilities

  • Application development components
  • Versioned runtime or build interfaces
  • Security and compatibility maintenance

Typical use

Used by software teams to build, run or maintain applications.

Deployment

Included in source projects, application dependencies, build systems or managed runtimes.

Lifecycle records

ReleaseBoundaryDate
Lifecycle policyOfficial lifecycle policy; no bounded date foundNot dated by publisher

Official sources

PARTIAL

Phoenix Framework official lifecycle source

Checked automatically.

Extracted 1 lifecycle record(s), including 0 bounded date record(s), from the registered official source.

Open publisher source

Package vulnerability advisories

Phoenix before 1.6.14 mishandles check_origin wildcarding

Fixed: 1.6.14

Phoenix: Unbounded channel joins per transport enables DoS over few connections

Fixed: 1.5.15, 1.6.17, 1.7.24, 1.8.9

Phoenix: Long-poll NDJSON body splitting causes large memory allocation

Fixed: 1.7.22, 1.8.6

Phoenix: Presence keys colliding with `Object.prototype` members break existence checks

Fixed: 1.5.15, 1.6.17, 1.7.24, 1.8.9

Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff

Fixed: 1.5.15, 1.6.17, 1.7.24, 1.8.9, 7f7b971c1ea0994e3fbd1c11ddb05e780bd38ad8, 89a1c4be161e436241e12b2378a719904b9bd96f, b90b22521465ece00eb5a19d5aa2b9465b209c85, beffc4da1e787e572121f68902c63daf4fe7d9c2

Long-poll NDJSON body splitting causes unbounded memory allocation in Phoenix

Fixed: 1.7.22, 1.8.6, 1a67c61ff9ce0a7711662ac7354861917a7c80f7, 912ea181fd247c21dbcc49fb97d0053b947d81bf

Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service

Fixed: 1.5.15, 1.6.17, 1.7.24, 1.8.9, c498ba8cf49f6accbbd0c643a5340b58db891218, d19ca0a8d9f82c130b7ed339b9f033433e2dea5e, a612100cd8a4279091abc1a2ef8fb98a6d01c0a1, 16e295d2fccab185d1292322e2bee5d46c725c8a