fix(broker/engine): the empty cbmod must not start the multiplexer #2478

bouda1 · 2025-06-20T12:59:43Z

Description

Two fixes:

engine can now read an old engine configuration (when cbmod was a module).
when engine reads the configuration to check it, it doesn't start the multiplexer (to avoid wrong logs).

coderabbitai · 2025-06-20T12:59:48Z

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)

coderabbit

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

github-actions · 2025-06-20T13:12:26Z

Checkmarx One – Scan Summary & Details – 0363e916-a938-4b10-ab17-5223d7e7ea7d

New Issues (254)

Checkmarx found the following issues in this Pull Request

Issue	Source File / Package	Checkmarx Insight
Buffer_Improper_Index_Access	/core/test/time/timerange.cc: 81	details The array index v at /core/test/time/timerange.cc in line 81 is used to reference an index of a cell of the array v at /core/test/time/timerange.... `ID: GLuI1ixVfY%2FEBL6VB8tjPmRLw1g%3D` Attack Vector
SQL_Injection	/test/my_plugin_bam.cc: 39	details Method main at line 39 of /test/my_plugin_bam.cc gets user input from the argv element. This element’s value then flows through the code withou... `ID: zqsnFEvJbRDuj8U9OI9kTSCrGxg%3D` Attack Vector
Second_Order_SQL_Injection	/test/db.cc: 443	details Method _run_script at line 443 of /test/db.cc gets database data from the buffer element. This element’s value then flows through the code with... `ID: SSmpAwJgqFIeRuMQfBhb1Cboe6E%3D` Attack Vector
Second_Order_SQL_Injection	/test/db.cc: 439	details Method _run_script at line 439 of /test/db.cc gets database data from the buffer element. This element’s value then flows through the code with... `ID: bV4oghEz7CbZc9biP6iApu3S7a0%3D` Attack Vector
Buffer_Overflow_boundedcpy2	/core/test/file/splitter/resume.cc: 43	details The size of the buffer used by SetUp in memset, at line 43 of /core/test/file/splitter/resume.cc, is not properly verified before writing data to ... `ID: rWX0d715tOQuKKQM2T5pCSPJYHQ%3D` Attack Vector
Off_by_One_Error	/test/bam/v2/main.cc: 355	details The size from array in /test/bam/v2/main.cc at line 355 does not correctly account for the actual size of the buffer, resulting in an incorrect ac... `ID: jpFtOooMSnvsDaOmVsOVBVME%2FcE%3D` Attack Vector
Off_by_One_Error	/test/bam/v2/main.cc: 355	details The size from array in /test/bam/v2/main.cc at line 355 does not correctly account for the actual size of the buffer, resulting in an incorrect ac... `ID: NNJo3L8XVPhrSEimgIhRjNLQ9mc%3D` Attack Vector
Path_Traversal	/test/write_into_file.cc: 21	details Method main at line 21 of /test/write_into_file.cc gets dynamic data from the argv element. This element’s value then flows through the code an... `ID: TwzYt1B4%2BXCa9T%2B2S%2F2RKt9GZ%2BY%3D` Attack Vector
Dangerous_Functions	/test/rrd_file.cc: 154	details The dangerous function, strlen, was found in use at line 154 in /test/rrd_file.cc file. Such functions may expose information and allow an attac... `ID: ziJGTyXpd2q3aiHoCfFnxN%2BTZu0%3D` Attack Vector
Dangerous_Functions	/test/rebuild_graphs.cc: 153	details The dangerous function, strcpy, was found in use at line 153 in /test/rebuild_graphs.cc file. Such functions may expose information and allow an... `ID: GggVfhESnfQJqnzSQn%2FR0jy59fo%3D` Attack Vector
Dangerous_Functions	/test/rebuild_graphs.cc: 139	details The dangerous function, strcpy, was found in use at line 139 in /test/rebuild_graphs.cc file. Such functions may expose information and allow an... `ID: v6P8NNNRiysWoFl6IBJ4uaqr1AY%3D` Attack Vector
Dangerous_Functions	/test/rebuild_graphs.cc: 146	details The dangerous function, strcpy, was found in use at line 146 in /test/rebuild_graphs.cc file. Such functions may expose information and allow an... `ID: MqxTjmK6T1gorZDNeyxDsZ8rJiw%3D` Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 200	details The dangerous function, strcpy, was found in use at line 200 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: 6Sg7zFTS3E3md64LhGREDRFvuoI%3D` Attack Vector
Dangerous_Functions	/test/rebuild_graphs.cc: 135	details The dangerous function, strcpy, was found in use at line 135 in /test/rebuild_graphs.cc file. Such functions may expose information and allow an... `ID: lqv8cBDrPL06XHdbntC%2FFB2NShc%3D` Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 164	details The dangerous function, strcpy, was found in use at line 164 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: T01HZZfjQoVM0rU7QYDTJa2WhKw%3D` Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 181	details The dangerous function, strcpy, was found in use at line 181 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: qxzwTQZ3%2Bu6sXKemppBFz77h1gY%3D` Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 156	details The dangerous function, strcpy, was found in use at line 156 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: bXcrXeetOPltZ%2B%2BiwQwaGoQJDaU%3D` Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 151	details The dangerous function, strcpy, was found in use at line 151 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: KapYkun40h3AbTOSAxiXdrHzHyI%3D` Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 170	details The dangerous function, strcpy, was found in use at line 170 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: chysAR8Xc6896xfW2om3qIGyqog%3D` Attack Vector
Dangerous_Functions	/test/meta_service.cc: 88	details The dangerous function, strcpy, was found in use at line 88 in /test/meta_service.cc file. Such functions may expose information and allow an at... `ID: 8KH4qjh%2Fn0cl5JL0bSelJgtENpI%3D` Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 146	details The dangerous function, strcpy, was found in use at line 146 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: ekGz4Z0UzKyiCFjsbejRm3gJ7jQ%3D`Attack Vector
Dangerous_Functions	/test/monitoring_to_rrd.cc: 142	details The dangerous function, strcpy, was found in use at line 142 in /test/monitoring_to_rrd.cc file. Such functions may expose information and allo... `ID: nzPeDSkC46GvkwigMIV7esri%2BpM%3D` Attack Vector
Dangerous_Functions	/test/meta_service.cc: 74	details The dangerous function, strcpy, was found in use at line 74 in /test/meta_service.cc file. Such functions may expose information and allow an at... `ID: mcg%2FFBo3PtAsotBuK7f6eZub4ys%3D` Attack Vector
Dangerous_Functions	/test/delete_graphs.cc: 132	details The dangerous function, strcpy, was found in use at line 132 in /test/delete_graphs.cc file. Such functions may expose information and allow an ... `ID: ICu7hrTZeyl1YbajZYz4eE3vt7M%3D` Attack Vector
Dangerous_Functions	/test/broker_extcmd.cc: 155	details The dangerous function, strlen, was found in use at line 155 in /test/broker_extcmd.cc file. Such functions may expose information and allow an ... `ID: U7en0gV1KlyUz9fYzCG8YoRwaN4%3D` Attack Vector
Dangerous_Functions	/test/bam_circular.cc: 95	details The dangerous function, strcpy, was found in use at line 95 in /test/bam_circular.cc file. Such functions may expose information and allow an at... `ID: 094Vkw9RRP3JOwmUBY5C%2FnVl%2BZ0%3D` Attack Vector
Dangerous_Functions	/test/delete_graphs.cc: 144	details The dangerous function, strcpy, was found in use at line 144 in /test/delete_graphs.cc file. Such functions may expose information and allow an ... `ID: QHUNEhpxHugukf8jlHZAlR9bbn0%3D` Attack Vector
Dangerous_Functions	/test/delete_graphs.cc: 138	details The dangerous function, strcpy, was found in use at line 138 in /test/delete_graphs.cc file. Such functions may expose information and allow an ... `ID: s27sKmGSBz2DiGfQR8g%2FblOMVCE%3D` Attack Vector
Dangerous_Functions	/test/bam_circular.cc: 88	details The dangerous function, strcpy, was found in use at line 88 in /test/bam_circular.cc file. Such functions may expose information and allow an at... `ID: LUDrkrRPJXHEPk2geJRUW%2FDPltY%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 198	details The dangerous function, strcpy, was found in use at line 198 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: C4glX16XjMOlw%2F3qPgK%2Bs4a2YU8%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 210	details The dangerous function, strcpy, was found in use at line 210 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: m%2FMLRniyT63%2FkCTFCZb5A4nYcWk%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 230	details The dangerous function, strcpy, was found in use at line 230 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: yiKai%2B%2FtORS20ewN4hLrfGMapOE%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 229	details The dangerous function, strlen, was found in use at line 229 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: Ricot5rKg%2BOmNk%2FwraZWJYlefWI%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 179	details The dangerous function, strlen, was found in use at line 179 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: Bx1O9x0PJ%2Bl6gXlfHGmXIMVyRZQ%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 180	details The dangerous function, strcpy, was found in use at line 180 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: hrnKDqR3Qt7DjjOr623QOW7Z%2BwU%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 190	details The dangerous function, strlen, was found in use at line 190 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: fPL%2B89TrQs6il2rDdTrmC1VQKEI%3D` Attack Vector
Dangerous_Functions	/test/bam_boolexp_retention.cc: 191	details The dangerous function, strcpy, was found in use at line 191 in /test/bam_boolexp_retention.cc file. Such functions may expose information and ... `ID: 7XhftF5Fas26RbsHEcyh28gNPJw%3D` Attack Vector
Dangerous_Functions	/test/rtmonitoring/v2/hosts.cc: 287	details The dangerous function, memcpy, was found in use at line 287 in /test/rtmonitoring/v2/hosts.cc file. Such functions may expose information and al... `ID: T%2FFMO0VVQTfr1CJrG01bJNHt%2B90%3D` Attack Vector
Dangerous_Functions	/test/rtmonitoring/v2/services.cc: 302	details The dangerous function, memcpy, was found in use at line 302 in /test/rtmonitoring/v2/services.cc file. Such functions may expose information and... `ID: wEHzGrP5OQXZDUrxDdICZs2VuHU%3D` Attack Vector
Dangerous_Functions	/test/predicate.cc: 116	details The dangerous function, memcpy, was found in use at line 116 in /test/predicate.cc file. Such functions may expose information and allow an attac... `ID: e9JoQF1oTYEp%2BHcUcHsClSCL72g%3D` Attack Vector
Dangerous_Functions	/test/predicate.cc: 115	details The dangerous function, memcpy, was found in use at line 115 in /test/predicate.cc file. Such functions may expose information and allow an attac... `ID: EX1ExKUJZ1zyi6fagOFyDxJWWng%3D` Attack Vector
Dangerous_Functions	/test/rtmonitoring/v2/comments.cc: 218	details The dangerous function, sprintf, was found in use at line 218 in /test/rtmonitoring/v2/comments.cc file. Such functions may expose information an... `ID: YQZ4VWSsT7QFrPNCags9Ucy%2BgXI%3D` Attack Vector
Dangerous_Functions	/tls/test/acceptor.cc: 186	details The dangerous function, strlen, was found in use at line 186 in /tls/test/acceptor.cc file. Such functions may expose information and allow an at... `ID: O9beS%2FU%2BEfPj1qBoeRKPo%2BY0bi0%3D` Attack Vector
Dangerous_Functions	/tls2/test/acceptor.cc: 192	details The dangerous function, strlen, was found in use at line 192 in /tls2/test/acceptor.cc file. Such functions may expose information and allow an a... `ID: hkejWsa2U2dZX8qn4wRiO5%2BXUME%3D` Attack Vector
Dangerous_Functions	/core/test/rpc/client.cc: 99	details The dangerous function, atoi, was found in use at line 99 in /core/test/rpc/client.cc file. Such functions may expose information and allow an at... `ID: e5Rv0CvD6QNod5%2B060qpNBTYY%2Bk%3D` Attack Vector
Dangerous_Functions	/test/google-benchmark/atoi.cc: 12	details The dangerous function, atoi, was found in use at line 12 in /test/google-benchmark/atoi.cc file. Such functions may expose information and allo... `ID: uYfAPW7TN9k6wMT4RCL9zMMmmmM%3D` Attack Vector
Dangerous_Functions	/core/sql/src/mysql_column.cc: 309	details The dangerous function, strncpy, was found in use at line 309 in /core/sql/src/mysql_column.cc file. Such functions may expose information and a... `ID: O3IvOUVLPFAkHdqEuLwCe8%2B9ZR8%3D` Attack Vector
Dangerous_Functions	/neb/test/randomize.cc: 68	details The dangerous function, strlen, was found in use at line 68 in /neb/test/randomize.cc file. Such functions may expose information and allow an at... `ID: i8Shye9dw%2BfrySL33m4jXPvTwhM%3D` Attack Vector
Dangerous_Functions	/neb/test/randomize.cc: 71	details The dangerous function, strncpy, was found in use at line 71 in /neb/test/randomize.cc file. Such functions may expose information and allow an a... `ID: qFq8VSdBSUsrzHcFCAd3ya60PUk%3D` Attack Vector
Dangerous_Functions	/test/google-benchmark/escape_str.cc: 75	details The dangerous function, strlen, was found in use at line 75 in /test/google-benchmark/escape_str.cc file. Such functions may expose information... `ID: jVQxHn6aF8td1E4n0lw9n3K8AA4%3D` Attack Vector
Dangerous_Functions	/core/test/cache/global_cache_test.cc: 134	details The dangerous function, strcpy, was found in use at line 134 in /core/test/cache/global_cache_test.cc file. Such functions may expose informati... `ID: ieFrneP2HINo1r4kW8MMDT5kunY%3D` Attack Vector
Dangerous_Functions	/bam/test/time/check_timeperiod.cc: 101	details The dangerous function, strlen, was found in use at line 101 in /bam/test/time/check_timeperiod.cc file. Such functions may expose information a... `ID: UuvX2jU9TFHcu1VpZnyBkHdvzuA%3D` Attack Vector
Dangerous_Functions	/core/bbdo/stream.cc: 116	details The dangerous function, strlen, was found in use at line 116 in /core/bbdo/stream.cc file. Such functions may expose information and allow an att... `ID: PRyx7600rOExoQfiJorq56UMGRE%3D` Attack Vector
Dangerous_Functions	/core/bbdo/stream.cc: 66	details The dangerous function, strlen, was found in use at line 66 in /core/bbdo/stream.cc file. Such functions may expose information and allow an atta... `ID: dk49BBZMyECW0M3oDrXMjs8lbX0%3D` Attack Vector
Dangerous_Functions	/bam/test/time/check_timeperiod.cc: 100	details The dangerous function, strlen, was found in use at line 100 in /bam/test/time/check_timeperiod.cc file. Such functions may expose information a... `ID: qtZQwhyiyD%2BVK5ITjm1GUJb6ZsQ%3D` Attack Vector
Dangerous_Functions	/bam/src/configuration/reader_v2.cc: 307	details The dangerous function, strlen, was found in use at line 307 in /bam/src/configuration/reader_v2.cc file. Such functions may expose information ... `ID: ILYde1iD9uVBsVIbNnmSsF1AJVk%3D` Attack Vector
Dangerous_Functions	/tls2/test/crypt-test.cc: 192	details The dangerous function, memcpy, was found in use at line 192 in /tls2/test/crypt-test.cc file. Such functions may expose information and allow a... `ID: bpUQZaII%2BtUlEop8psVYlscYavA%3D` Attack Vector
Dangerous_Functions	/tls2/test/anon-test.cc: 144	details The dangerous function, memcpy, was found in use at line 144 in /tls2/test/anon-test.cc file. Such functions may expose information and allow an... `ID: brVtBXCayb1Tkb5c8KTPCd%2BaHrQ%3D` Attack Vector
Dangerous_Functions	/tls2/test/acceptor.cc: 190	details The dangerous function, sprintf, was found in use at line 190 in /tls2/test/acceptor.cc file. Such functions may expose information and allow an ... `ID: 5s0fnjfsKU3X%2FQIWHaMFbBfauW0%3D` Attack Vector
Dangerous_Functions	/tls/test/acceptor.cc: 152	details The dangerous function, sprintf, was found in use at line 152 in /tls/test/acceptor.cc file. Such functions may expose information and allow an a... `ID: XTfmmWZ3554SQC9KhsI0dTE%2FDLE%3D` Attack Vector
Dangerous_Functions	/tls/test/anon-test.cc: 144	details The dangerous function, memcpy, was found in use at line 144 in /tls/test/anon-test.cc file. Such functions may expose information and allow an ... `ID: W8Nz0R74pyxe%2BUFIwM%2Bi1ifQZ4A%3D` Attack Vector
Dangerous_Functions	/tls/test/crypt-test.cc: 189	details The dangerous function, memcpy, was found in use at line 189 in /tls/test/crypt-test.cc file. Such functions may expose information and allow an... `ID: Jq44OkrFFQgZvHINnnDRcPY8fvI%3D` Attack Vector
Dangerous_Functions	/tls2/test/acceptor.cc: 154	details The dangerous function, sprintf, was found in use at line 154 in /tls2/test/acceptor.cc file. Such functions may expose information and allow an ... `ID: e0cWQQOqx62S8AIanEDQ%2FF2NNas%3D` Attack Vector 8000
Dangerous_Functions	/tls/test/acceptor.cc: 184	details The dangerous function, sprintf, was found in use at line 184 in /tls/test/acceptor.cc file. Such functions may expose information and allow an a... `ID: 6mYvJ9zjuupYChEMGbbWSBMyQTg%3D` Attack Vector
Dangerous_Functions	/core/multiplexing/test/muxer/read.cc: 58	details The dangerous function, memcpy, was found in use at line 58 in /core/multiplexing/test/muxer/read.cc file. Such functions may expose information ... `ID: 6MP%2FIgvJVmBPzNFLkP%2B69AiihK4%3D` Attack Vector
Dangerous_Functions	/core/multiplexing/test/muxer/read.cc: 72	details The dangerous function, memcpy, was found in use at line 72 in /core/multiplexing/test/muxer/read.cc file. Such functions may expose information ... `ID: eIrBueC0KBkRMxaViUZZDFpDuTc%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1085	details The dangerous function, sscanf, was found in use at line 1085 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: Mwa4j9qULE%2BRFQ8tD4IzotxyZzs%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1103	details The dangerous function, sscanf, was found in use at line 1103 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: IaYUvMXQ38DS52cGlSBtqCtLt7w%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1112	details The dangerous function, sscanf, was found in use at line 1112 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: %2B2NJvU2nlKZzHQO%2BkbhhorytXQY%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1129	details The dangerous function, sscanf, was found in use at line 1129 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: nmslxwlYrBq%2FPoi65%2FaW%2FNPhUqQ%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1145	details The dangerous function, sscanf, was found in use at line 1145 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: KEjD%2FPAiZh6IekTsOzxs2xFDBXE%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1155	details The dangerous function, sscanf, was found in use at line 1155 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: 0L3Om6VdZfvaWpZ9z1I79arS09E%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1005	details The dangerous function, sscanf, was found in use at line 1005 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: nL%2BhcUFQeEvZpOToqnYiU5LdsUQ%3D` Attack Vector
Dangerous_Functions	/core/src/time/daterange.cc: 1059	details The dangerous function, sscanf, was found in use at line 1059 in /core/src/time/daterange.cc file. Such functions may expose information and allo... `ID: zJreppfZYLwY3jEejBvjJHrKZkA%3D` Attack Vector

More results are available on the CxOne platform

…2478) * fix(broker/engine): the empty cbmod must not start the multiplexer * fix(tests): bench tests disabled on ci REFS: MON-173354

…2478) * fix(broker/engine): the empty cbmod must not start the multiplexer * fix(tests): bench tests disabled on ci REFS: MON-173368

fix(broker/engine): the empty cbmod must not start the multiplexer

d031766

bouda1 requested review from a team as code owners June 20, 2025 12:59

bouda1 requested review from sdepassio, lucie-tirand and jean-christophe81 and removed request for a team June 20, 2025 12:59

bouda1 requested review from sechkem and removed request for sdepassio and lucie-tirand June 20, 2025 12:59

github-actions bot added skip-workflow-monitoring-agent skip-workflow-centreon-collect labels Jun 20, 2025

github-actions bot added the skip-workflow-broker-analysis label Jun 20, 2025

fix(tests): bench tests disabled on ci

62794ef

github-actions bot removed the skip-workflow-broker-analysis label Jun 20, 2025

sechkem approved these changes Jun 20, 2025

View reviewed changes

bouda1 merged commit 3bfbd3f into release-25.05-next Jun 20, 2025
23 of 25 checks passed

bouda1 deleted the MON-173354-new-engine-can-read-old-conf branch June 20, 2025 13:47

bouda1 added a commit that referenced this pull request Jun 20, 2025

fix(broker/engine): the empty cbmod must not start the multiplexer (#…

7343b0d

…2478) * fix(broker/engine): the empty cbmod must not start the multiplexer * fix(tests): bench tests disabled on ci REFS: MON-173354

github-actions bot added the skip-workflow-broker-analysis label Jun 20, 2025

bouda1 added a commit that referenced this pull request Jun 20, 2025

fix(broker/engine): the empty cbmod must not start the multiplexer (#…

4fc9ec1

…2478) * fix(broker/engine): the empty cbmod must not start the multiplexer * fix(tests): bench tests disabled on ci REFS: MON-173368

bouda1 added a commit that referenced this pull request Jun 20, 2025

fix(broker/engine): the empty cbmod must not start the multiplexer (#…

9d1331a

…2478) * fix(broker/engine): the empty cbmod must not start the multiplexer * fix(tests): bench tests disabled on ci REFS: MON-173368

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(broker/engine): the empty cbmod must not start the multiplexer #2478

fix(broker/engine): the empty cbmod must not start the multiplexer #2478

Uh oh!

Uh oh!

Review skipped