calibre up to 6.18.x html_input.py link_to_local_path server-side request forgery

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 marked as problematic has been reported in calibre up to 6.18.x. Impacted is the function link_to_local_path of the file ebooks/conversion/plugins/html_input.py. The manipulation leads to an unknown weakness. This vulnerability is traded as CVE-2023-46303. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in calibre up to 6.18.x and classified as problematic. This issue affects the function link_to_local_path of the file ebooks/conversion/plugins/html_input.py. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. The impact remains unknown. The summary by CVE is:

link_to_local_path in ebooks/conversion/plugins/html_input.py in calibre before 6.19.0 can, by default, add resources outside of the document root.

The weakness was shared 10/23/2023. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-46303 since 10/22/2023. Technical details are known, but no exploit is available.

Upgrading to version 6.19.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-50525). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

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: Server-side request forgery
CWE: CWE-918
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: calibre 6.19.0

Timelineinfo

10/22/2023 🔍
10/23/2023 +1 days 🔍
10/23/2023 +0 days 🔍
02/14/2026 +845 days 🔍

Sourcesinfo

Advisory: github.com
Status: Confirmed

CVE: CVE-2023-46303 (🔍)
GCVE (CVE): GCVE-0-2023-46303
GCVE (VulDB): GCVE-100-243149
EUVD: 🔍

Entryinfo

Created: 10/23/2023 07:25
Updated: 02/14/2026 21:39
Changes: 10/23/2023 07:25 (39), 11/12/2023 17:06 (12), 02/14/2026 21:39 (16)
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!