gsd-2020-12831
Vulnerability from gsd
Modified
2023-12-13 01:21
Details
** DISPUTED ** An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file.
Aliases
Aliases
CVE-2020-12831


To clipboard 

{
   GSD: {
      alias: "CVE-2020-12831",
      description: "** DISPUTED ** An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file.",
      id: "GSD-2020-12831",
      references: [
         "https://www.suse.com/security/cve/CVE-2020-12831.html",
         "https://access.redhat.com/errata/RHSA-2020:4619",
         "https://linux.oracle.com/cve/CVE-2020-12831.html",
      ],
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2020-12831",
         ],
         details: "** DISPUTED ** An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file.",
         id: "GSD-2020-12831",
         modified: "2023-12-13T01:21:49.742845Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "cve@mitre.org",
            ID: "CVE-2020-12831",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "n/a",
                              version: {
                                 version_data: [
                                    {
                                       version_value: "n/a",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "n/a",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "** DISPUTED ** An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file.",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "n/a",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://bugzilla.redhat.com/show_bug.cgi?id=1830805",
                  refsource: "MISC",
                  url: "https://bugzilla.redhat.com/show_bug.cgi?id=1830805",
               },
               {
                  name: "https://github.com/FRRouting/frr/pull/6383",
                  refsource: "MISC",
                  url: "https://github.com/FRRouting/frr/pull/6383",
               },
            ],
         },
      },
      "nvd.nist.gov": {
         cve: {
            configurations: [
               {
                  nodes: [
                     {
                        cpeMatch: [
                           {
                              criteria: "cpe:2.3:a:linuxfoundation:free_range_routing:*:*:*:*:*:*:*:*",
                              matchCriteriaId: "3634E0FB-3635-4554-A95F-A09F45F29A0A",
                              versionEndIncluding: "7.3.1",
                              vulnerable: true,
                           },
                        ],
                        negate: false,
                        operator: "OR",
                     },
                  ],
               },
            ],
            descriptions: [
               {
                  lang: "en",
                  value: "An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file",
               },
               {
                  lang: "es",
                  value: "** EN DISPUTA ** Se detectó un problema en FRRouting FRR (también se conoce como Free Range Routing) versiones hasta 7.3.1. Cuando se utiliza la funcionalidad split-config, crea un archivo de configuración vacío con permisos predeterminados world-readable, conllevando a un posible filtrado de información por medio del archivo tools/frr.in y tools/frrcommon.sh.in. NOTA: algunos terceros consideran esto un error de usuario, no una vulnerabilidad, porque los permisos están bajo el control del usuario antes de que alguna información confidencial este presente en el archivo.",
               },
            ],
            id: "CVE-2020-12831",
            lastModified: "2024-04-11T01:06:52.430",
            metrics: {
               cvssMetricV2: [
                  {
                     acInsufInfo: false,
                     baseSeverity: "MEDIUM",
                     cvssData: {
                        accessComplexity: "MEDIUM",
                        accessVector: "NETWORK",
                        authentication: "NONE",
                        availabilityImpact: "NONE",
                        baseScore: 4.3,
                        confidentialityImpact: "PARTIAL",
                        integrityImpact: "NONE",
                        vectorString: "AV:N/AC:M/Au:N/C:P/I:N/A:N",
                        version: "2.0",
                     },
                     exploitabilityScore: 8.6,
                     impactScore: 2.9,
                     obtainAllPrivilege: false,
                     obtainOtherPrivilege: false,
                     obtainUserPrivilege: false,
                     source: "nvd@nist.gov",
                     type: "Primary",
                     userInteractionRequired: false,
                  },
               ],
               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",
                  },
               ],
            },
            published: "2020-05-13T18:15:12.047",
            references: [
               {
                  source: "cve@mitre.org",
                  tags: [
                     "Exploit",
                     "Issue Tracking",
                     "Vendor Advisory",
                  ],
                  url: "https://bugzilla.redhat.com/show_bug.cgi?id=1830805",
               },
               {
                  source: "cve@mitre.org",
                  tags: [
                     "Patch",
                     "Third Party Advisory",
                  ],
                  url: "https://github.com/FRRouting/frr/pull/6383",
               },
            ],
            sourceIdentifier: "cve@mitre.org",
            vulnStatus: "Modified",
            weaknesses: [
               {
                  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.