plv8 3.2.1 Autovacuum status code

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

Summaryinfo

A vulnerability categorized as problematic has been discovered in plv8 3.2.1. This affects an unknown function of the component Autovacuum. Such manipulation leads to status code. This vulnerability is referenced as CVE-2024-1713. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in plv8 3.2.1. Affected by this issue is an unknown functionality of the component Autovacuum. The manipulation with an unknown input leads to a status code vulnerability. Using CWE to declare the problem leads to CWE-394. The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product. Impacted is confidentiality, integrity, and availability. CVE summarizes:

A user who can create objects in a database with plv8 3.2.1 installed is able to cause deferred triggers to execute as the Superuser during autovacuum.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2024-1713 since 02/21/2024. The exploitation is known to be difficult. The attack may be launched remotely. The exploitation requires an enhanced level of successful authentication. There are neither technical details nor an exploit publicly available.

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

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.6

VulDB Base Score: 4.1
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 7.2
CNA Vector (Google Inc.): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Status code
CWE: CWE-394 / CWE-393
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

02/21/2024 🔍
03/15/2024 +23 days 🔍
03/15/2024 +0 days 🔍
03/15/2024 +0 days 🔍

Sourcesinfo

Advisory: GHSA-r7m9-grw7-vcc4
Status: Not defined

CVE: CVE-2024-1713 (🔍)
GCVE (CVE): GCVE-0-2024-1713
GCVE (VulDB): GCVE-100-256880

Entryinfo

Created: 03/15/2024 01:05
Changes: 03/15/2024 01:05 (47)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

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!