| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in BibTeX. The impacted element is an unknown function of the file latex.php. The manipulation of the argument bibtexrootrel leads to an unknown weakness. No exploit is available.
Details
A vulnerability, which was classified as critical, has been found in BibTeX (the affected version is unknown). This issue affects an unknown code of the file latex.php. The manipulation of the argument bibtexrootrel with an unknown input leads to a unknown weakness. The impact remains unknown.
The weakness was published 04/22/2007 by InyeXion (Website). The advisory is shared at archives.neohapsis.com. Technical details are known, but no exploit is available.
After even before and not, there has been an exploit disclosed. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:latex.php it is possible to find vulnerable targets with Google Hacking.
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 OSVDB (35624†). Similar entries are available at VDB-85563, VDB-85564, VDB-85566 and VDB-85567. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Google Hack: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/22/2007 🔍04/22/2007 🔍
05/05/2007 🔍
05/08/2016 🔍
05/08/2016 🔍
Sources
Advisory: archives.neohapsis.comResearcher: InyeXion
Status: Not defined
GCVE (VulDB): GCVE-100-85565
OSVDB: 35624 - bibtex mase latex.php bibtexrootrel Parameter Remote File Inclusion
See also: 🔍
Entry
Created: 05/08/2016 21:55Changes: 05/08/2016 21:55 (40)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.