{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31138 exists.","fix":"No fix has been published for CVE-2022-31138 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31138 is a high-severity command injection vulnerability in mailcow-dockerized, published on 11 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31138 and fix it if it is affected.\n\nWhat it is: CVE-2022-31138 is a high-severity command injection vulnerability in mailcow-dockerized, published on 11 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31138 exists.\n\nAffected product: mailcow-dockerized. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-31138/ (Markdown: https://insights.sbomify.com/CVE-2022-31138/index.md)","id":"CVE-2022-31138","markdown":"https://insights.sbomify.com/CVE-2022-31138/index.md","name":"CVE-2022-31138","record":{"aliases":["GHSA-vx9w-h33p-5vhc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"mailcow mail server","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by manipulating specific sync job parameters in mailcow, requiring an upgrade to patch.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mailcow\\","vendor":"mailcow"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"mailcow is a mailserver suite. Prior to mailcow-dockerized version 2022-06a, an extended privilege vulnerability can be exploited by manipulating the custom parameters regexmess, skipmess, regexflag, delete2foldersonly, delete2foldersbutnot, regextrans2, pipemess, or maxlinelengthcmd to execute arbitrary code. Users should update their mailcow instances with the `update.sh` script in the mailcow root directory to 2022-06a or newer to receive a patch for this issue. As a temporary workaround, the Syncjob ACL can be removed from all mailbox users, preventing changes to those settings.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-07-11","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-07-11T06:53:24Z","kind":"github_poc","ref":"https://github.com/ly1g3/Mailcow-CVE-2022-31138","stars":2,"title":"Mailcow CVE-2022-31138 RCE"}],"tier":"weaponised"},"has_fix":false,"headline":"OS Command Injection in mailcow","id":"CVE-2022-31138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"No security checking for UnsafeAccess.getInstance() in UnsafeAccessor","id":"CVE-2022-31139"},"packages":[],"prev":{"headline":"Unauthenticated Remote Code Execution in Roxy-WI","id":"CVE-2022-31137"},"products":["mailcow-dockerized"],"published":"2022-07-11","related":[{"cvss_score":9.1,"headline":"mailcow: dockerized vulnerable to SSTI in Quota and Quarantine Notification Template","id":"CVE-2025-53909","kev_date_added":null,"published":"2025-07-17"},{"cvss_score":8.8,"headline":"Mailcow Docker Container Exposure to Local Network","id":"CVE-2024-24760","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":8.8,"headline":"Manipulation of Internal Dovecot Variables in mailcow via crafted Passwords","id":"CVE-2023-34108","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-31245","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-8928","kev_date_added":null,"published":"2017-05-14"},{"cvss_score":8.3,"headline":"mailcow-dockerized XSS Vulnerability in Quarantine UI Allows Unauthorized Access and Data Manipulation","id":"CVE-2023-49077","kev_date_added":null,"published":"2023-11-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["mailcow"]},"summary":"Attackers can execute arbitrary code by manipulating specific sync job parameters in mailcow, requiring an upgrade to patch.","url":"https://insights.sbomify.com/CVE-2022-31138/"}