thorsten phpmyfaq up to 3.1.8 missing secure attribute

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.
5.8$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in thorsten phpmyfaq up to 3.1.8. This vulnerability affects unknown code. The manipulation leads to missing secure attribute. This vulnerability is listed as CVE-2022-4409. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in thorsten phpmyfaq up to 3.1.8 (Content Management System). This issue affects some unknown functionality. The manipulation with an unknown input leads to a missing secure attribute vulnerability. Using CWE to declare the problem leads to CWE-614. The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session. Impacted is confidentiality. The summary by CVE is:

Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository thorsten/phpmyfaq prior to 3.1.9.

The weakness was presented 12/11/2022. The advisory is shared at huntr.dev. The identification of this vulnerability is CVE-2022-4409 since 12/11/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1539 for this issue.

Upgrading to version 3.1.9 eliminates this vulnerability. Applying a patch 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.8
VulDB Meta Temp Score: 5.8

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CNA Base Score: 6.3
CNA Vector (huntr.dev): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Missing secure attribute
CWE: CWE-614 / CWE-1004 / CWE-732
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: phpmyfaq 3.1.9
Patch: github.com

Timelineinfo

12/11/2022 🔍
12/11/2022 +0 days 🔍
12/11/2022 +0 days 🔍
01/02/2023 +22 days 🔍

Sourcesinfo

Product: github.com

Advisory: huntr.dev
Status: Confirmed

CVE: CVE-2022-4409 (🔍)
GCVE (CVE): GCVE-0-2022-4409
GCVE (VulDB): GCVE-100-215273

Entryinfo

Created: 12/11/2022 19:10
Updated: 01/02/2023 14:44
Changes: 12/11/2022 19:10 (40), 01/02/2023 14:44 (21)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!