pfSense CE 2.6.0 weak password

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

Summaryinfo

A vulnerability, which was classified as critical, was found in pfSense CE 2.6.0. This issue affects some unknown processing. Such manipulation leads to weak password. This vulnerability is referenced as CVE-2023-29974. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in pfSense CE 2.6.0 (Firewall Software). Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a weak password vulnerability. Using CWE to declare the problem leads to CWE-521. The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. Impacted is confidentiality. CVE summarizes:

An issue discovered in Pfsense CE version 2.6.0 allows attackers to compromise user accounts via weak password requirements.

The weakness was published 11/08/2023. The advisory is shared for download at esecforte.com. This vulnerability is handled as CVE-2023-29974 since 04/07/2023. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1552.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-33504). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.6

VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CNA Base Score: 9.8
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Weak password
CWE: CWE-521
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/07/2023 🔍
11/08/2023 +215 days 🔍
11/08/2023 +0 days 🔍
12/16/2025 +769 days 🔍

Sourcesinfo

Advisory: esecforte.com
Status: Not defined

CVE: CVE-2023-29974 (🔍)
GCVE (CVE): GCVE-0-2023-29974
GCVE (VulDB): GCVE-100-244820
EUVD: 🔍

Entryinfo

Created: 11/08/2023 22:35
Updated: 12/16/2025 23:48
Changes: 11/08/2023 22:35 (37), 11/09/2023 12:52 (2), 12/05/2023 12:44 (11), 09/05/2024 00:30 (27), 12/16/2025 23:48 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

 Anonymous User (+0)
3 years ago
Good morning,
Could you align to the official NVD Nist cpe "cpe:2.3:a:pfsense:pfsense"?
For CVE-2023-29973 cve_id NIST also used "cpe:2.3:a:pfsense:pfsense"
We would appreciate it very much.

Best regards,
TeamCERT
 VulDB Community Team3 years ago
Thank you, we have just aligned the CPE.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!