mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-07 11:07:05 +00:00
Auto-Update: 2024-03-05T15:01:09.291630+00:00
This commit is contained in:
parent
488ddae222
commit
8fe54b4582
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47082",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.120",
|
||||
"lastModified": "2024-03-04T18:15:07.120",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47083",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.193",
|
||||
"lastModified": "2024-03-04T18:15:07.193",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47084",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.253",
|
||||
"lastModified": "2024-03-04T18:15:07.253",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47085",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.317",
|
||||
"lastModified": "2024-03-04T18:15:07.317",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47086",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.393",
|
||||
"lastModified": "2024-03-04T18:15:07.393",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47087",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.457",
|
||||
"lastModified": "2024-03-04T18:15:07.457",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47088",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.510",
|
||||
"lastModified": "2024-03-04T18:15:07.510",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47089",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.560",
|
||||
"lastModified": "2024-03-04T18:15:07.560",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47090",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.610",
|
||||
"lastModified": "2024-03-04T18:15:07.610",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47091",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.670",
|
||||
"lastModified": "2024-03-04T18:15:07.670",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47092",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.723",
|
||||
"lastModified": "2024-03-04T18:15:07.723",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47093",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.787",
|
||||
"lastModified": "2024-03-04T18:15:07.787",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47094",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.837",
|
||||
"lastModified": "2024-03-04T18:15:07.837",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47095",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.907",
|
||||
"lastModified": "2024-03-04T18:15:07.907",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47096",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:07.960",
|
||||
"lastModified": "2024-03-04T18:15:07.960",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47097",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:08.017",
|
||||
"lastModified": "2024-03-04T18:15:08.017",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47098",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:08.090",
|
||||
"lastModified": "2024-03-04T18:15:08.090",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47099",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:08.153",
|
||||
"lastModified": "2024-03-04T18:15:08.153",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47100",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:08.267",
|
||||
"lastModified": "2024-03-04T18:15:08.267",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47101",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:08.450",
|
||||
"lastModified": "2024-03-04T18:15:08.450",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47102",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:08.600",
|
||||
"lastModified": "2024-03-04T18:15:08.600",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47103",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T18:15:08.667",
|
||||
"lastModified": "2024-03-04T18:15:08.667",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47104",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T19:15:18.643",
|
||||
"lastModified": "2024-03-04T19:15:18.643",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47105",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T19:15:18.707",
|
||||
"lastModified": "2024-03-04T19:15:18.707",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47106",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T19:15:18.750",
|
||||
"lastModified": "2024-03-04T19:15:18.750",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47107",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T19:15:18.793",
|
||||
"lastModified": "2024-03-04T19:15:18.793",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2021-47108",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-04T19:15:18.837",
|
||||
"lastModified": "2024-03-04T19:15:18.837",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2022-43890",
|
||||
"sourceIdentifier": "psirt@us.ibm.com",
|
||||
"published": "2024-03-04T16:15:48.890",
|
||||
"lastModified": "2024-03-04T16:15:48.890",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,12 +2,12 @@
|
||||
"id": "CVE-2022-48629",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-05T12:15:45.707",
|
||||
"lastModified": "2024-03-05T12:15:45.707",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qcom-rng - ensure buffer for generate is completely filled\n\nThe generate function in struct rng_alg expects that the destination\nbuffer is completely filled if the function returns 0. qcom_rng_read()\ncan run into a situation where the buffer is partially filled with\nrandomness and the remaining part of the buffer is zeroed since\nqcom_rng_generate() doesn't check the return value. This issue can\nbe reproduced by running the following from libkcapi:\n\n kcapi-rng -b 9000000 > OUTFILE\n\nThe generated OUTFILE will have three huge sections that contain all\nzeros, and this is caused by the code where the test\n'val & PRNG_STATUS_DATA_AVAIL' fails.\n\nLet's fix this issue by ensuring that qcom_rng_read() always returns\nwith a full buffer if the function returns success. Let's also have\nqcom_rng_generate() return the correct value.\n\nHere's some statistics from the ent project\n(https://www.fourmilab.ch/random/) that shows information about the\nquality of the generated numbers:\n\n $ ent -c qcom-random-before\n Value Char Occurrences Fraction\n 0 606748 0.067416\n 1 33104 0.003678\n 2 33001 0.003667\n ...\n 253 \ufffd 32883 0.003654\n 254 \ufffd 33035 0.003671\n 255 \ufffd 33239 0.003693\n\n Total: 9000000 1.000000\n\n Entropy = 7.811590 bits per byte.\n\n Optimum compression would reduce the size\n of this 9000000 byte file by 2 percent.\n\n Chi square distribution for 9000000 samples is 9329962.81, and\n randomly would exceed this value less than 0.01 percent of the\n times.\n\n Arithmetic mean value of data bytes is 119.3731 (127.5 = random).\n Monte Carlo value for Pi is 3.197293333 (error 1.77 percent).\n Serial correlation coefficient is 0.159130 (totally uncorrelated =\n 0.0).\n\nWithout this patch, the results of the chi-square test is 0.01%, and\nthe numbers are certainly not random according to ent's project page.\nThe results improve with this patch:\n\n $ ent -c qcom-random-after\n Value Char Occurrences Fraction\n 0 35432 0.003937\n 1 35127 0.003903\n 2 35424 0.003936\n ...\n 253 \ufffd 35201 0.003911\n 254 \ufffd 34835 0.003871\n 255 \ufffd 35368 0.003930\n\n Total: 9000000 1.000000\n\n Entropy = 7.999979 bits per byte.\n\n Optimum compression would reduce the size\n of this 9000000 byte file by 0 percent.\n\n Chi square distribution for 9000000 samples is 258.77, and randomly\n would exceed this value 42.24 percent of the times.\n\n Arithmetic mean value of data bytes is 127.5006 (127.5 = random).\n Monte Carlo value for Pi is 3.141277333 (error 0.01 percent).\n Serial correlation coefficient is 0.000468 (totally uncorrelated =\n 0.0).\n\nThis change was tested on a Nexus 5 phone (msm8974 SoC)."
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qcom-rng - ensure buffer for generate is completely filled\n\nThe generate function in struct rng_alg expects that the destination\nbuffer is completely filled if the function returns 0. qcom_rng_read()\ncan run into a situation where the buffer is partially filled with\nrandomness and the remaining part of the buffer is zeroed since\nqcom_rng_generate() doesn't check the return value. This issue can\nbe reproduced by running the following from libkcapi:\n\n kcapi-rng -b 9000000 > OUTFILE\n\nThe generated OUTFILE will have three huge sections that contain all\nzeros, and this is caused by the code where the test\n'val & PRNG_STATUS_DATA_AVAIL' fails.\n\nLet's fix this issue by ensuring that qcom_rng_read() always returns\nwith a full buffer if the function returns success. Let's also have\nqcom_rng_generate() return the correct value.\n\nHere's some statistics from the ent project\n(https://www.fourmilab.ch/random/) that shows information about the\nquality of the generated numbers:\n\n $ ent -c qcom-random-before\n Value Char Occurrences Fraction\n 0 606748 0.067416\n 1 33104 0.003678\n 2 33001 0.003667\n ...\n 253 ? 32883 0.003654\n 254 ? 33035 0.003671\n 255 ? 33239 0.003693\n\n Total: 9000000 1.000000\n\n Entropy = 7.811590 bits per byte.\n\n Optimum compression would reduce the size\n of this 9000000 byte file by 2 percent.\n\n Chi square distribution for 9000000 samples is 9329962.81, and\n randomly would exceed this value less than 0.01 percent of the\n times.\n\n Arithmetic mean value of data bytes is 119.3731 (127.5 = random).\n Monte Carlo value for Pi is 3.197293333 (error 1.77 percent).\n Serial correlation coefficient is 0.159130 (totally uncorrelated =\n 0.0).\n\nWithout this patch, the results of the chi-square test is 0.01%, and\nthe numbers are certainly not random according to ent's project page.\nThe results improve with this patch:\n\n $ ent -c qcom-random-after\n Value Char Occurrences Fraction\n 0 35432 0.003937\n 1 35127 0.003903\n 2 35424 0.003936\n ...\n 253 ? 35201 0.003911\n 254 ? 34835 0.003871\n 255 ? 35368 0.003930\n\n Total: 9000000 1.000000\n\n Entropy = 7.999979 bits per byte.\n\n Optimum compression would reduce the size\n of this 9000000 byte file by 0 percent.\n\n Chi square distribution for 9000000 samples is 258.77, and randomly\n would exceed this value 42.24 percent of the times.\n\n Arithmetic mean value of data bytes is 127.5006 (127.5 = random).\n Monte Carlo value for Pi is 3.141277333 (error 0.01 percent).\n Serial correlation coefficient is 0.000468 (totally uncorrelated =\n 0.0).\n\nThis change was tested on a Nexus 5 phone (msm8974 SoC)."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2022-48630",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-03-05T12:15:45.780",
|
||||
"lastModified": "2024-03-05T12:15:45.780",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-32331",
|
||||
"sourceIdentifier": "psirt@us.ibm.com",
|
||||
"published": "2024-03-04T19:15:18.893",
|
||||
"lastModified": "2024-03-04T19:15:18.893",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-38360",
|
||||
"sourceIdentifier": "psirt@us.ibm.com",
|
||||
"published": "2024-03-04T18:15:08.743",
|
||||
"lastModified": "2024-03-04T18:15:08.743",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-38362",
|
||||
"sourceIdentifier": "psirt@us.ibm.com",
|
||||
"published": "2024-03-04T16:15:49.130",
|
||||
"lastModified": "2024-03-04T16:15:49.130",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-41827",
|
||||
"sourceIdentifier": "psirt@lenovo.com",
|
||||
"published": "2024-03-04T22:15:46.330",
|
||||
"lastModified": "2024-03-04T22:15:46.330",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-41829",
|
||||
"sourceIdentifier": "psirt@lenovo.com",
|
||||
"published": "2024-03-04T22:15:46.547",
|
||||
"lastModified": "2024-03-04T22:15:46.547",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-42419",
|
||||
"sourceIdentifier": "info@cybellum.com",
|
||||
"published": "2024-03-05T06:15:52.820",
|
||||
"lastModified": "2024-03-05T06:15:52.820",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45591",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:45.833",
|
||||
"lastModified": "2024-03-05T12:15:45.833",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45592",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:46.037",
|
||||
"lastModified": "2024-03-05T12:15:46.037",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45593",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:46.213",
|
||||
"lastModified": "2024-03-05T12:15:46.213",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45594",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:46.493",
|
||||
"lastModified": "2024-03-05T12:15:46.493",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45595",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:46.717",
|
||||
"lastModified": "2024-03-05T12:15:46.717",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45596",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:46.913",
|
||||
"lastModified": "2024-03-05T12:15:46.913",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45597",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:47.107",
|
||||
"lastModified": "2024-03-05T12:15:47.107",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45598",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:47.277",
|
||||
"lastModified": "2024-03-05T12:15:47.277",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45599",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:47.433",
|
||||
"lastModified": "2024-03-05T12:15:47.433",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-45600",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:47.613",
|
||||
"lastModified": "2024-03-05T12:15:47.613",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-49546",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.077",
|
||||
"lastModified": "2024-03-05T00:15:52.077",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-49547",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.150",
|
||||
"lastModified": "2024-03-05T00:15:52.150",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-49548",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.203",
|
||||
"lastModified": "2024-03-05T00:15:52.203",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-49968",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.253",
|
||||
"lastModified": "2024-03-05T00:15:52.253",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-49969",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.303",
|
||||
"lastModified": "2024-03-05T00:15:52.303",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-49970",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.350",
|
||||
"lastModified": "2024-03-05T00:15:52.350",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-52432",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:08.070",
|
||||
"lastModified": "2024-03-05T05:15:08.070",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-5451",
|
||||
"sourceIdentifier": "psirt@forcepoint.com",
|
||||
"published": "2024-03-04T16:15:49.490",
|
||||
"lastModified": "2024-03-04T16:15:49.490",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-5456",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T11:15:07.657",
|
||||
"lastModified": "2024-03-05T11:15:07.657",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-5457",
|
||||
"sourceIdentifier": "prodsec@nozominetworks.com",
|
||||
"published": "2024-03-05T12:15:47.793",
|
||||
"lastModified": "2024-03-05T12:15:47.793",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2023-6068",
|
||||
"sourceIdentifier": "psirt@arista.com",
|
||||
"published": "2024-03-04T20:15:50.267",
|
||||
"lastModified": "2024-03-04T20:15:50.267",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
55
CVE-2023/CVE-2023-71xx/CVE-2023-7103.json
Normal file
55
CVE-2023/CVE-2023-71xx/CVE-2023-7103.json
Normal file
@ -0,0 +1,55 @@
|
||||
{
|
||||
"id": "CVE-2023-7103",
|
||||
"sourceIdentifier": "iletisim@usom.gov.tr",
|
||||
"published": "2024-03-05T13:15:06.940",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Authentication Bypass by Primary Weakness vulnerability in ZKSoftware Biometric Security Solutions UFace 5 allows Authentication Bypass.This issue affects UFace 5: through 12022024.\n\n"
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "iletisim@usom.gov.tr",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "HIGH",
|
||||
"availabilityImpact": "HIGH",
|
||||
"baseScore": 9.8,
|
||||
"baseSeverity": "CRITICAL"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 5.9
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "iletisim@usom.gov.tr",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-305"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://www.usom.gov.tr/bildirim/tr-24-0173",
|
||||
"source": "iletisim@usom.gov.tr"
|
||||
}
|
||||
]
|
||||
}
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-0698",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:25.460",
|
||||
"lastModified": "2024-03-05T02:15:25.460",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-0825",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:25.653",
|
||||
"lastModified": "2024-03-05T02:15:25.653",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1088",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:25.813",
|
||||
"lastModified": "2024-03-05T02:15:25.813",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1093",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:25.970",
|
||||
"lastModified": "2024-03-05T02:15:25.970",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1095",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:26.130",
|
||||
"lastModified": "2024-03-05T02:15:26.130",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1178",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:26.290",
|
||||
"lastModified": "2024-03-05T02:15:26.290",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1285",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:26.447",
|
||||
"lastModified": "2024-03-05T02:15:26.447",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1316",
|
||||
"sourceIdentifier": "contact@wpscan.com",
|
||||
"published": "2024-03-04T21:15:07.007",
|
||||
"lastModified": "2024-03-04T21:15:07.007",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1319",
|
||||
"sourceIdentifier": "contact@wpscan.com",
|
||||
"published": "2024-03-04T21:15:07.083",
|
||||
"lastModified": "2024-03-04T21:15:07.083",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1381",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:26.620",
|
||||
"lastModified": "2024-03-05T02:15:26.620",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1478",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:26.773",
|
||||
"lastModified": "2024-03-05T02:15:26.773",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1731",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:26.937",
|
||||
"lastModified": "2024-03-05T02:15:26.937",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1769",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:27.093",
|
||||
"lastModified": "2024-03-05T02:15:27.093",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1782",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-05T02:15:27.253",
|
||||
"lastModified": "2024-03-05T02:15:27.253",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-1936",
|
||||
"sourceIdentifier": "security@mozilla.org",
|
||||
"published": "2024-03-04T22:15:46.733",
|
||||
"lastModified": "2024-03-04T22:15:46.733",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20829",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:08.703",
|
||||
"lastModified": "2024-03-05T05:15:08.703",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20830",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:09.093",
|
||||
"lastModified": "2024-03-05T05:15:09.093",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20831",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:09.403",
|
||||
"lastModified": "2024-03-05T05:15:09.403",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20832",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:09.793",
|
||||
"lastModified": "2024-03-05T05:15:09.793",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20833",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T08:15:39.260",
|
||||
"lastModified": "2024-03-05T08:15:39.260",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20834",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:10.207",
|
||||
"lastModified": "2024-03-05T05:15:10.207",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20835",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:10.473",
|
||||
"lastModified": "2024-03-05T05:15:10.473",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20836",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:10.813",
|
||||
"lastModified": "2024-03-05T05:15:10.813",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20837",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:11.150",
|
||||
"lastModified": "2024-03-05T05:15:11.150",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20838",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:11.517",
|
||||
"lastModified": "2024-03-05T05:15:11.517",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20839",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:12.007",
|
||||
"lastModified": "2024-03-05T05:15:12.007",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20840",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:12.363",
|
||||
"lastModified": "2024-03-05T05:15:12.363",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-20841",
|
||||
"sourceIdentifier": "mobile.security@samsung.com",
|
||||
"published": "2024-03-05T05:15:12.717",
|
||||
"lastModified": "2024-03-05T05:15:12.717",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-2048",
|
||||
"sourceIdentifier": "security@hashicorp.com",
|
||||
"published": "2024-03-04T20:15:50.690",
|
||||
"lastModified": "2024-03-04T20:15:50.690",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-21815",
|
||||
"sourceIdentifier": "disclosures@gallagher.com",
|
||||
"published": "2024-03-05T03:15:06.060",
|
||||
"lastModified": "2024-03-05T03:15:06.060",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-21838",
|
||||
"sourceIdentifier": "disclosures@gallagher.com",
|
||||
"published": "2024-03-05T03:15:06.280",
|
||||
"lastModified": "2024-03-05T03:15:06.280",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-2168",
|
||||
"sourceIdentifier": "cna@vuldb.com",
|
||||
"published": "2024-03-04T21:15:07.137",
|
||||
"lastModified": "2024-03-04T21:15:07.137",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
55
CVE-2024/CVE-2024-21xx/CVE-2024-2188.json
Normal file
55
CVE-2024/CVE-2024-21xx/CVE-2024-2188.json
Normal file
@ -0,0 +1,55 @@
|
||||
{
|
||||
"id": "CVE-2024-2188",
|
||||
"sourceIdentifier": "cve-coordination@incibe.es",
|
||||
"published": "2024-03-05T13:15:07.203",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Cross-Site Scripting (XSS) vulnerability stored in TP-Link Archer AX50 affecting firmware version 1.0.11 build 2022052. This vulnerability could allow an unauthenticated attacker to create a port mapping rule via a SOAP request and store a malicious JavaScript payload within that rule, which could result in an execution of the JavaScript payload when the rule is loaded."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "cve-coordination@incibe.es",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L",
|
||||
"attackVector": "LOCAL",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "REQUIRED",
|
||||
"scope": "CHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "LOW",
|
||||
"baseScore": 6.1,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 1.8,
|
||||
"impactScore": 3.7
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "cve-coordination@incibe.es",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-79"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://www.incibe.es/en/incibe-cert/notices/aviso/cross-site-scripting-vulnerability-tp-link-archer-ax50",
|
||||
"source": "cve-coordination@incibe.es"
|
||||
}
|
||||
]
|
||||
}
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-22188",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T02:15:27.443",
|
||||
"lastModified": "2024-03-05T02:15:27.443",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-22383",
|
||||
"sourceIdentifier": "disclosures@gallagher.com",
|
||||
"published": "2024-03-05T03:15:06.470",
|
||||
"lastModified": "2024-03-05T03:15:06.470",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-25164",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.400",
|
||||
"lastModified": "2024-03-05T00:15:52.400",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-25269",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T01:15:06.780",
|
||||
"lastModified": "2024-03-05T01:15:06.780",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-25731",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T00:15:52.457",
|
||||
"lastModified": "2024-03-05T00:15:52.457",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-26333",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T08:15:39.500",
|
||||
"lastModified": "2024-03-05T08:15:39.500",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-26334",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T09:15:45.040",
|
||||
"lastModified": "2024-03-05T09:15:45.040",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-26335",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T09:15:45.100",
|
||||
"lastModified": "2024-03-05T09:15:45.100",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
@ -2,8 +2,8 @@
|
||||
"id": "CVE-2024-26337",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-05T09:15:45.143",
|
||||
"lastModified": "2024-03-05T09:15:45.143",
|
||||
"vulnStatus": "Received",
|
||||
"lastModified": "2024-03-05T13:41:01.900",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user