fkie_cve-2024-46897
Vulnerability from fkie_nvd
Published
2024-10-18 06:15
Modified
2024-10-22 14:09
Severity ?
3.8 (Low) - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
Summary
Incorrect permission assignment for critical resource issue exists in Exment v6.1.4 and earlier and Exment v5.0.11 and earlier. A logged-in user with the permission of table management may obtain and/or alter the information of the unauthorized table.
References
vultures@jpcert.or.jphttps://exment.net/docs/#/weakness/20241010_2Vendor Advisory
vultures@jpcert.or.jphttps://exment.net/vulnerability-correspondence-version-6-1-5-and-5-0-12-released/Vendor Advisory
vultures@jpcert.or.jphttps://jvn.jp/en/jp/JVN74538317/Third Party Advisory
Impacted products
Vendor Product Version
exceedone exment *
exceedone exment *


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:exceedone:exment:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "2549CC6B-4C04-4F38-975A-898DFB2A1256",
                     versionEndExcluding: "5.0.11",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:exceedone:exment:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "8FC82718-B952-41A6-9530-6D0119C504CE",
                     versionEndExcluding: "6.1.4",
                     versionStartIncluding: "6.0.0",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Incorrect permission assignment for critical resource issue exists in Exment v6.1.4 and earlier and Exment v5.0.11 and earlier. A logged-in user with the permission of table management may obtain and/or alter the information of the unauthorized table.",
      },
      {
         lang: "es",
         value: "Existe un problema de asignación de permisos incorrectos para recursos críticos en Exment v6.1.4 y versiones anteriores y Exment v5.0.11 y versiones anteriores. Un usuario que haya iniciado sesión con el permiso de administración de la tabla puede obtener o modificar la información de la tabla no autorizada.",
      },
   ],
   id: "CVE-2024-46897",
   lastModified: "2024-10-22T14:09:46.913",
   metrics: {
      cvssMetricV30: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 3.8,
               baseSeverity: "LOW",
               confidentialityImpact: "LOW",
               integrityImpact: "LOW",
               privilegesRequired: "HIGH",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N",
               version: "3.0",
            },
            exploitabilityScore: 1.2,
            impactScore: 2.5,
            source: "vultures@jpcert.or.jp",
            type: "Secondary",
         },
      ],
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 3.8,
               baseSeverity: "LOW",
               confidentialityImpact: "LOW",
               integrityImpact: "LOW",
               privilegesRequired: "HIGH",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N",
               version: "3.1",
            },
            exploitabilityScore: 1.2,
            impactScore: 2.5,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2024-10-18T06:15:04.813",
   references: [
      {
         source: "vultures@jpcert.or.jp",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://exment.net/docs/#/weakness/20241010_2",
      },
      {
         source: "vultures@jpcert.or.jp",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://exment.net/vulnerability-correspondence-version-6-1-5-and-5-0-12-released/",
      },
      {
         source: "vultures@jpcert.or.jp",
         tags: [
            "Third Party Advisory",
         ],
         url: "https://jvn.jp/en/jp/JVN74538317/",
      },
   ],
   sourceIdentifier: "vultures@jpcert.or.jp",
   vulnStatus: "Analyzed",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-732",
            },
         ],
         source: "vultures@jpcert.or.jp",
         type: "Secondary",
      },
      {
         description: [
            {
               lang: "en",
               value: "CWE-732",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.