gsd-2022-24734
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
MyBB is a free and open source forum software. In affected versions the Admin CP's Settings management module does not validate setting types correctly on insertion and update, making it possible to add settings of supported type `php` with PHP code, executed on on _Change Settings_ pages. This results in a Remote Code Execution (RCE) vulnerability. The vulnerable module requires Admin CP access with the `Can manage settings?` permission. MyBB's Settings module, which allows administrators to add, edit, and delete non-default settings, stores setting data in an options code string ($options_code; mybb_settings.optionscode database column) that identifies the setting type and its options, separated by a new line character (\n). In MyBB 1.2.0, support for setting type php was added, for which the remaining part of the options code is PHP code executed on Change Settings pages (reserved for plugins and internal use). MyBB 1.8.30 resolves this issue. There are no known workarounds.
Aliases
Aliases



{
   GSD: {
      alias: "CVE-2022-24734",
      description: " MyBB is a free and open source forum software. In affected versions the Admin CP's Settings management module does not validate setting types correctly on insertion and update, making it possible to add settings of supported type `php` with PHP code, executed on on _Change Settings_ pages. This results in a Remote Code Execution (RCE) vulnerability. The vulnerable module requires Admin CP access with the `Can manage settings?` permission. MyBB's Settings module, which allows administrators to add, edit, and delete non-default settings, stores setting data in an options code string ($options_code; mybb_settings.optionscode database column) that identifies the setting type and its options, separated by a new line character (\\n). In MyBB 1.2.0, support for setting type php was added, for which the remaining part of the options code is PHP code executed on Change Settings pages (reserved for plugins and internal use). MyBB 1.8.30 resolves this issue. There are no known workarounds.",
      id: "GSD-2022-24734",
      references: [
         "https://packetstormsecurity.com/files/cve/CVE-2022-24734",
      ],
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2022-24734",
         ],
         details: "MyBB is a free and open source forum software. In affected versions the Admin CP's Settings management module does not validate setting types correctly on insertion and update, making it possible to add settings of supported type `php` with PHP code, executed on on _Change Settings_ pages. This results in a Remote Code Execution (RCE) vulnerability. The vulnerable module requires Admin CP access with the `Can manage settings?` permission. MyBB's Settings module, which allows administrators to add, edit, and delete non-default settings, stores setting data in an options code string ($options_code; mybb_settings.optionscode database column) that identifies the setting type and its options, separated by a new line character (\\n). In MyBB 1.2.0, support for setting type php was added, for which the remaining part of the options code is PHP code executed on Change Settings pages (reserved for plugins and internal use). MyBB 1.8.30 resolves this issue. There are no known workarounds.",
         id: "GSD-2022-24734",
         modified: "2023-12-13T01:19:43.588737Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "security-advisories@github.com",
            ID: "CVE-2022-24734",
            STATE: "PUBLIC",
            TITLE: "Remote code execution in mybb",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "mybb",
                              version: {
                                 version_data: [
                                    {
                                       version_value: ">= 1.2.0, < 1.8.30",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "mybb",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "MyBB is a free and open source forum software. In affected versions the Admin CP's Settings management module does not validate setting types correctly on insertion and update, making it possible to add settings of supported type `php` with PHP code, executed on on _Change Settings_ pages. This results in a Remote Code Execution (RCE) vulnerability. The vulnerable module requires Admin CP access with the `Can manage settings?` permission. MyBB's Settings module, which allows administrators to add, edit, and delete non-default settings, stores setting data in an options code string ($options_code; mybb_settings.optionscode database column) that identifies the setting type and its options, separated by a new line character (\\n). In MyBB 1.2.0, support for setting type php was added, for which the remaining part of the options code is PHP code executed on Change Settings pages (reserved for plugins and internal use). MyBB 1.8.30 resolves this issue. There are no known workarounds.",
               },
            ],
         },
         impact: {
            cvss: {
               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",
            },
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "CWE-94: Improper Control of Generation of Code ('Code Injection')",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://github.com/mybb/mybb/security/advisories/GHSA-876v-gwgh-w57f",
                  refsource: "CONFIRM",
                  url: "https://github.com/mybb/mybb/security/advisories/GHSA-876v-gwgh-w57f",
               },
               {
                  name: "https://github.com/mybb/mybb/commit/92012b9831b330714b9f9b4646a98784113489c1",
                  refsource: "MISC",
                  url: "https://github.com/mybb/mybb/commit/92012b9831b330714b9f9b4646a98784113489c1",
               },
               {
                  name: "https://mybb.com/versions/1.8.30/",
                  refsource: "MISC",
                  url: "https://mybb.com/versions/1.8.30/",
               },
               {
                  name: "https://www.zerodayinitiative.com/advisories/ZDI-22-503/",
                  refsource: "MISC",
                  url: "https://www.zerodayinitiative.com/advisories/ZDI-22-503/",
               },
               {
                  name: "http://packetstormsecurity.com/files/167082/MyBB-1.8.29-Remote-Code-Execution.html",
                  refsource: "MISC",
                  url: "http://packetstormsecurity.com/files/167082/MyBB-1.8.29-Remote-Code-Execution.html",
               },
               {
                  name: "http://packetstormsecurity.com/files/167333/MyBB-Admin-Control-Remote-Code-Execution.html",
                  refsource: "MISC",
                  url: "http://packetstormsecurity.com/files/167333/MyBB-Admin-Control-Remote-Code-Execution.html",
               },
            ],
         },
         source: {
            advisory: "GHSA-876v-gwgh-w57f",
            discovery: "UNKNOWN",
         },
      },
      "nvd.nist.gov": {
         configurations: {
            CVE_data_version: "4.0",
            nodes: [
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:mybb:mybb:*:*:*:*:*:*:*:*",
                        cpe_name: [],
                        versionEndExcluding: "1.8.30",
                        versionStartIncluding: "1.2.0",
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
            ],
         },
         cve: {
            CVE_data_meta: {
               ASSIGNER: "security-advisories@github.com",
               ID: "CVE-2022-24734",
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "en",
                     value: "MyBB is a free and open source forum software. In affected versions the Admin CP's Settings management module does not validate setting types correctly on insertion and update, making it possible to add settings of supported type `php` with PHP code, executed on on _Change Settings_ pages. This results in a Remote Code Execution (RCE) vulnerability. The vulnerable module requires Admin CP access with the `Can manage settings?` permission. MyBB's Settings module, which allows administrators to add, edit, and delete non-default settings, stores setting data in an options code string ($options_code; mybb_settings.optionscode database column) that identifies the setting type and its options, separated by a new line character (\\n). In MyBB 1.2.0, support for setting type php was added, for which the remaining part of the options code is PHP code executed on Change Settings pages (reserved for plugins and internal use). MyBB 1.8.30 resolves this issue. There are no known workarounds.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "en",
                           value: "CWE-94",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://mybb.com/versions/1.8.30/",
                     refsource: "MISC",
                     tags: [
                        "Release Notes",
                        "Vendor Advisory",
                     ],
                     url: "https://mybb.com/versions/1.8.30/",
                  },
                  {
                     name: "https://github.com/mybb/mybb/commit/92012b9831b330714b9f9b4646a98784113489c1",
                     refsource: "MISC",
                     tags: [
                        "Patch",
                        "Third Party Advisory",
                     ],
                     url: "https://github.com/mybb/mybb/commit/92012b9831b330714b9f9b4646a98784113489c1",
                  },
                  {
                     name: "https://github.com/mybb/mybb/security/advisories/GHSA-876v-gwgh-w57f",
                     refsource: "CONFIRM",
                     tags: [
                        "Patch",
                        "Third Party Advisory",
                     ],
                     url: "https://github.com/mybb/mybb/security/advisories/GHSA-876v-gwgh-w57f",
                  },
                  {
                     name: "https://www.zerodayinitiative.com/advisories/ZDI-22-503/",
                     refsource: "MISC",
                     tags: [
                        "Third Party Advisory",
                        "VDB Entry",
                        "Vendor Advisory",
                     ],
                     url: "https://www.zerodayinitiative.com/advisories/ZDI-22-503/",
                  },
                  {
                     name: "http://packetstormsecurity.com/files/167082/MyBB-1.8.29-Remote-Code-Execution.html",
                     refsource: "MISC",
                     tags: [
                        "Exploit",
                        "Third Party Advisory",
                        "VDB Entry",
                     ],
                     url: "http://packetstormsecurity.com/files/167082/MyBB-1.8.29-Remote-Code-Execution.html",
                  },
                  {
                     name: "http://packetstormsecurity.com/files/167333/MyBB-Admin-Control-Remote-Code-Execution.html",
                     refsource: "MISC",
                     tags: [
                        "Exploit",
                        "Third Party Advisory",
                     ],
                     url: "http://packetstormsecurity.com/files/167333/MyBB-Admin-Control-Remote-Code-Execution.html",
                  },
               ],
            },
         },
         impact: {
            baseMetricV2: {
               acInsufInfo: false,
               cvssV2: {
                  accessComplexity: "LOW",
                  accessVector: "NETWORK",
                  authentication: "SINGLE",
                  availabilityImpact: "PARTIAL",
                  baseScore: 6.5,
                  confidentialityImpact: "PARTIAL",
                  integrityImpact: "PARTIAL",
                  vectorString: "AV:N/AC:L/Au:S/C:P/I:P/A:P",
                  version: "2.0",
               },
               exploitabilityScore: 8,
               impactScore: 6.4,
               obtainAllPrivilege: false,
               obtainOtherPrivilege: false,
               obtainUserPrivilege: false,
               severity: "MEDIUM",
               userInteractionRequired: false,
            },
            baseMetricV3: {
               cvssV3: {
                  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,
            },
         },
         lastModifiedDate: "2022-09-30T13:22Z",
         publishedDate: "2022-03-09T22:15Z",
      },
   },
}


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.


Loading…

Loading…

Loading…

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.