Phoenix up to 1.6.13 Wilrdcard socket/transport.ex check_origin privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Phoenix up to 1.6.13. This affects the function check_origin of the file socket/transport.ex of the component Wilrdcard Handler. The manipulation leads to an unknown weakness. This vulnerability is uniquely identified as CVE-2022-42975. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Phoenix up to 1.6.13 and classified as problematic. This issue affects the function check_origin of the file socket/transport.ex of the component Wilrdcard Handler. The impact remains unknown. The summary by CVE is:

socket/transport.ex in Phoenix before 1.6.14 mishandles check_origin wildcarding. NOTE: LiveView applications are unaffected by default because of the presence of a LiveView CSRF token.

The weakness was disclosed 10/17/2022 as 6e7185b33a59e0b1d1c0b4223adf340a73e963ae. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-42975 since 10/17/2022. Technical details are known, but no exploit is available.

Upgrading to version 1.6.14 eliminates this vulnerability. Applying the patch 6e7185b33a59e0b1d1c0b4223adf340a73e963ae is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Phoenix 1.6.14
Patch: 6e7185b33a59e0b1d1c0b4223adf340a73e963ae

Timelineinfo

10/17/2022 🔍
10/17/2022 +0 days 🔍
10/17/2022 +0 days 🔍
05/10/2025 +936 days 🔍

Sourcesinfo

Advisory: 6e7185b33a59e0b1d1c0b4223adf340a73e963ae
Status: Confirmed

CVE: CVE-2022-42975 (🔍)
GCVE (CVE): GCVE-0-2022-42975
GCVE (VulDB): GCVE-100-211037

Entryinfo

Created: 10/17/2022 12:46
Updated: 05/10/2025 05:57
Changes: 10/17/2022 12:46 (43), 11/09/2022 15:26 (11), 05/10/2025 05:57 (15)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!