admin/cvelist
1
0
Fork 0
mirror of https://github.com/CVEProject/cvelist.git synced 2025-05-08 19:46:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

"-Synchronized-Data."

Browse Source
This commit is contained in:
CVE Team 2022-09-14 17:00:35 +00:00
parent 3397d2af6f
commit fe1976e1c1
No known key found for this signature in database
GPG Key ID: E3252B3D49582C98
17 changed files with 250 additions and 177 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

180
2021/38xxx/CVE-2021-38924.json
View File

@ -1,93 +1,93 @@
{
"data_format" : "MITRE",
"affects" : {
"vendor" : {
"vendor_data" : [
{
"vendor_name" : "IBM",
"product" : {
"product_data" : [
{
"version" : {
"version_data" : [
{
"version_value" : "7.6.1.1"
},
{
"version_value" : "7.6.1.2"
}
]
},
"product_name" : "Maximo Asset Management"
}
]
}
}
]
}
},
"CVE_data_meta" : {
"ID" : "CVE-2021-38924",
"ASSIGNER" : "psirt@us.ibm.com",
"DATE_PUBLIC" : "2022-09-13T00:00:00",
"STATE" : "PUBLIC"
},
"data_type" : "CVE",
"description" : {
"description_data" : [
{
"value" : "IBM Maximo Asset Management 7.6.1.1 and 7.6.1.2 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 210163.",
"lang" : "eng"
}
]
},
"data_version" : "4.0",
"impact" : {
"cvssv3" : {
"TM" : {
"E" : "U",
"RC" : "C",
"RL" : "O"
},
"BM" : {
"A" : "N",
"C" : "L",
"UI" : "N",
"AV" : "N",
"I" : "N",
"AC" : "L",
"S" : "U",
"SCORE" : "5.300",
"PR" : "N"
}
}
},
"problemtype" : {
"problemtype_data" : [
{
"description" : [
{
"value" : "Obtain Information",
"lang" : "eng"
}
"data_format": "MITRE",
"affects": {
"vendor": {
"vendor_data": [
{
"vendor_name": "IBM",
"product": {
"product_data": [
{
"version": {
"version_data": [
{
"version_value": "7.6.1.1"
},
{
"version_value": "7.6.1.2"
}
]
},
"product_name": "Maximo Asset Management"
}
]
}
}
]
}
]
},
"references" : {
"reference_data" : [
{
"name" : "https://www.ibm.com/support/pages/node/6620059",
"url" : "https://www.ibm.com/support/pages/node/6620059",
"title" : "IBM Security Bulletin 6620059 (Maximo Asset Management)",
"refsource" : "CONFIRM"
},
{
"name" : "ibm-maximo-cve202138924-info-disc (210163)",
"url" : "https://exchange.xforce.ibmcloud.com/vulnerabilities/210163",
"title" : "X-Force Vulnerability Report",
"refsource" : "XF"
}
]
}
}
},
"CVE_data_meta": {
"ID": "CVE-2021-38924",
"ASSIGNER": "psirt@us.ibm.com",
"DATE_PUBLIC": "2022-09-13T00:00:00",
"STATE": "PUBLIC"
},
"data_type": "CVE",
"description": {
"description_data": [
{
"value": "IBM Maximo Asset Management 7.6.1.1 and 7.6.1.2 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 210163.",
"lang": "eng"
}
]
},
"data_version": "4.0",
"impact": {
"cvssv3": {
"TM": {
"E": "U",
"RC": "C",
"RL": "O"
},
"BM": {
"A": "N",
"C": "L",
"UI": "N",
"AV": "N",
"I": "N",
"AC": "L",
"S": "U",
"SCORE": "5.300",
"PR": "N"
}
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"value": "Obtain Information",
"lang": "eng"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://www.ibm.com/support/pages/node/6620059",
"url": "https://www.ibm.com/support/pages/node/6620059",
"title": "IBM Security Bulletin 6620059 (Maximo Asset Management)",
"refsource": "CONFIRM"
},
{
"name": "ibm-maximo-cve202138924-info-disc (210163)",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/210163",
"title": "X-Force Vulnerability Report",
"refsource": "XF"
}
]
}
}

7
2022/0xxx/CVE-2022-0029.json
View File

@ -67,7 +67,7 @@
"credit": [
{
"lang": "eng",
"value": "Palo Alto Networks thanks Diego García of INCIDE for discovering and reporting this issue."
"value": "Palo Alto Networks thanks Diego Garc\u00eda of INCIDE for discovering and reporting this issue."
}
],
"data_format": "MITRE",
@ -121,8 +121,9 @@
"references": {
"reference_data": [
{
"refsource": "CONFIRM",
"url": "https://security.paloaltonetworks.com/CVE-2022-0029"
"refsource": "MISC",
"url": "https://security.paloaltonetworks.com/CVE-2022-0029",
"name": "https://security.paloaltonetworks.com/CVE-2022-0029"
}
]
},

5
2022/33xxx/CVE-2022-33733.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/33xxx/CVE-2022-33734.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36829.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36830.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36831.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36832.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36833.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36834.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36835.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36836.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36837.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36838.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36839.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

5
2022/36xxx/CVE-2022-36840.json
View File

@ -74,6 +74,11 @@
"refsource": "MISC",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year==2022&month=08"
},
{
"refsource": "MISC",
"name": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=08"
}
]
},

168
2022/3xxx/CVE-2022-3212.json
View File

@ -1,91 +1,93 @@
{
"data_type": "CVE",
"data_format": "MITRE",
"data_version": "4.0",
"CVE_data_meta": {
"ID": "CVE-2022-3212",
"ASSIGNER": "security@jfrog.com",
"TITLE": "DoS in axum-core due to missing request size limit",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"vendor_name": "tokio-rs",
"product": {
"product_data": [
{
"product_name": "axum-core",
"version": {
"version_data": [
{
"version_name": "",
"version_affected": "<",
"version_value": "0.2.8",
"platform": ""
},
{
"version_name": "",
"version_affected": "=",
"version_value": "0.3.0-rc.1",
"platform": ""
"data_type": "CVE",
"data_format": "MITRE",
"data_version": "4.0",
"CVE_data_meta": {
"ID": "CVE-2022-3212",
"ASSIGNER": "security@jfrog.com",
"TITLE": "DoS in axum-core due to missing request size limit",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"vendor_name": "tokio-rs",
"product": {
"product_data": [
{
"product_name": "axum-core",
"version": {
"version_data": [
{
"version_name": "",
"version_affected": "<",
"version_value": "0.2.8",
"platform": ""
},
{
"version_name": "",
"version_affected": "=",
"version_value": "0.3.0-rc.1",
"platform": ""
}
]
}
}
]
}
]
}
}
]
}
}
]
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-770 Allocation of Resources Without Limits or Throttling"
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-770 Allocation of Resources Without Limits or Throttling"
}
]
}
]
}
]
},
"description": {
"description_data": [
{
"lang": "eng",
"value": "<bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash.\nThis also applies to these extractors which used Bytes::from_request internally:\naxum::extract::Form\naxum::extract::Json\nString"
}
]
},
"references": {
"reference_data": [
{
"refsource": "CONFIRM",
"url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/"
},
{
"refsource": "CONFIRM",
"url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"
}
]
},
"impact": {
"cvss": {
"version": "3.1",
"attackVector": "NETWORK",
"attackComplexity": "LOW",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"availabilityImpact": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"baseScore": 7.5,
"baseSeverity": "HIGH"
},
"description": {
"description_data": [
{
"lang": "eng",
"value": "<bytes::Bytes as axum_core::extract::FromRequest>::from_request would not, by default, set a limit for the size of the request body. That meant if a malicious peer would send a very large (or infinite) body your server might run out of memory and crash. This also applies to these extractors which used Bytes::from_request internally: axum::extract::Form axum::extract::Json String"
}
]
},
"references": {
"reference_data": [
{
"refsource": "MISC",
"url": "https://research.jfrog.com/vulnerabilities/axum-core-dos/",
"name": "https://research.jfrog.com/vulnerabilities/axum-core-dos/"
},
{
"refsource": "MISC",
"url": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html",
"name": "https://rustsec.org/advisories/RUSTSEC-2022-0055.html"
}
]
},
"impact": {
"cvss": {
"version": "3.1",
"attackVector": "NETWORK",
"attackComplexity": "LOW",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"availabilityImpact": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"baseScore": 7.5,
"baseSeverity": "HIGH"
}
}
}
}