Xorur 2.41
Approved changes feed: RSS · Atom
cpe:2.3:a:xorur:xorur:2.41:*:*:*:*:*:*:*
part: a version: 2.41 update: *
| Vendor | Xorur (f7721b47-39a8-5766-a399-347b3a3eccc1) |
|---|---|
| Product | Xorur (bc9d6db6-6f57-583a-b0b3-d2551b5714c8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-19041 |
not_vulnerable | 2026-06-08 05:13:21.351036 |
Details available
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by the underlying system. It is possible to achieve this by modifying the values in the files.SUM file (which are used for integrity control) and injecting malicious code into the upgrade.sh file.
Published: 2019-11-17T20:52:34.000Z
Updated: 2024-08-05T02:09:37.581Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.