| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Nagios 3.4.4/3.5.1. It has been rated as problematic. Impacted is an unknown function of the file html/rss-newsfeed.php. The manipulation leads to link following. This vulnerability is referenced as CVE-2013-4214. The attack can only be performed from a local environment. No exploit is available.
Details
A vulnerability was found in Nagios 3.4.4/3.5.1 (Log Management Software) and classified as problematic. This issue affects an unknown function of the file html/rss-newsfeed.php. The manipulation with an unknown input leads to a link following vulnerability. Using CWE to declare the problem leads to CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. Impacted is confidentiality, and integrity. The summary by CVE is:
rss-newsfeed.php in Nagios Core 3.4.4, 3.5.1, and earlier, when MAGPIE_CACHE_ON is set to 1, allows local users to overwrite arbitrary files via a symlink attack on /tmp/magpie_cache.
The weakness was published 08/07/2013 by Grant Murhphy with Red Hat as not defined mailinglist post (oss-sec). The advisory is shared at seclists.org. The public release happened without involvement of the project team. The identification of this vulnerability is CVE-2013-4214 since 06/12/2013. An attack has to be approached locally. The successful exploitation requires a simple authentication. Technical details are known, but no exploit is available.
By approaching the search of inurl:html/rss-newsfeed.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 (96086†). Similar entry is available at VDB-9904. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.4
VulDB Temp Score: 4.4
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Link followingCWE: CWE-59
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
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
06/12/2013 🔍08/07/2013 🔍
08/12/2013 🔍
11/23/2013 🔍
05/21/2021 🔍
Sources
Advisory: seclists.orgResearcher: Grant Murhphy
Organization: Red Hat
Status: Not defined
Confirmation: 🔍
CVE: CVE-2013-4214 (🔍)
GCVE (CVE): GCVE-0-2013-4214
GCVE (VulDB): GCVE-100-9905
SecurityFocus: 61747
OSVDB: 96086 - Nagios html/rss-newsfeed.php Insecure Temporary File Symlink Arbitrary File Overwrite
See also: 🔍
Entry
Created: 08/12/2013 15:36Updated: 05/21/2021 10:31
Changes: 08/12/2013 15:36 (49), 06/07/2017 15:07 (1), 05/21/2021 10:26 (2), 05/21/2021 10:31 (7)
Complete: 🔍
Committer:
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.