Apostrophe CMS up to 3.3.1 session expiration

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

Summaryinfo

A vulnerability was found in Apostrophe CMS up to 3.3.1. It has been classified as problematic. This affects an unknown part. This manipulation causes session expiration. This vulnerability is handled as CVE-2021-25979. The attack can be initiated remotely. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability has been found in Apostrophe CMS up to 3.3.1 (Content Management System) and classified as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a session expiration vulnerability. The CWE definition for the vulnerability is CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." As an impact it is known to affect confidentiality.

The weakness was released 11/09/2021 as c211b211f9f4303a77a307cf41aac9b4ef8d2c7c. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2021-25979 since 01/22/2021. The technical details are unknown and an exploit is not publicly available.

Applying the patch c211b211f9f4303a77a307cf41aac9b4ef8d2c7c is able to eliminate this problem. The bugfix is ready for download at github.com.

Statistical analysis made it clear that VulDB provides the best quality 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: 6.7
VulDB Meta Temp Score: 6.6

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

NVD Base Score: 6.5
NVD Vector: 🔍

CNA Base Score: 9.8
CNA Vector (WhiteSource): 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Session expiration
CWE: CWE-613
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: Patch
Status: 🔍

0-Day Time: 🔍

Patch: c211b211f9f4303a77a307cf41aac9b4ef8d2c7c

Timelineinfo

01/22/2021 🔍
11/09/2021 +291 days 🔍
11/09/2021 +0 days 🔍
11/11/2021 +2 days 🔍

Sourcesinfo

Advisory: c211b211f9f4303a77a307cf41aac9b4ef8d2c7c
Status: Confirmed

CVE: CVE-2021-25979 (🔍)
GCVE (CVE): GCVE-0-2021-25979
GCVE (VulDB): GCVE-100-186331

Entryinfo

Created: 11/09/2021 07:08
Updated: 11/11/2021 14:31
Changes: 11/09/2021 07:08 (51), 11/11/2021 14:25 (1), 11/11/2021 14:30 (17), 11/11/2021 14:31 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!