main to dev

[dev-callgent]

Pull Request Template

Description

Please include a summary of the change and which issue is fixed. Include the relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue number)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the DCO 1.1 as described in CONTRIBUTING.md.

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

To fix the prototype pollution issue in the _deepMerge function, we need to ensure that the function does not copy the special properties __proto__ and constructor. Additionally, we should ensure that only own properties of the target object are merged recursively.

• Modify the _deepMerge function to skip the properties __proto__ and constructor.
• Ensure that only own properties of the target object are merged recursively.

To fix the prototype pollution issue, we need to ensure that the _deepMerge function does not allow the special properties __proto__ and constructor to be copied from the source object to the target object. This can be achieved by adding a check to skip these properties during the merge process.

To fix the prototype pollution issue, we need to ensure that the _deepMerge function does not allow properties like __proto__ and constructor to be copied from the source object to the target object. Additionally, we should ensure that only own properties of the source object are copied.

The best way to fix this is to:

1. Add a check to skip properties named __proto__ and constructor.
2. Ensure that only own properties of the source object are copied.

To fix the problem, we need to ensure that the taskId parameter is a string before it is used in the _getTaskId method. This can be done by adding a type check in the EventObject constructor. If the taskId is not a string, we can handle it appropriately, such as by throwing an error or setting a default value.

To fix the problem, we need to ensure that the constructed file paths are contained within a safe root directory. This can be achieved by normalizing the path using path.resolve and then checking that the normalized path starts with the root directory. If the path is not within the root directory, we should reject the operation.

1. Normalize the dir parameter using path.resolve.
2. Check that the normalized path starts with the root directory (this.UPLOAD_BASE_DIR).
3. If the check fails, throw an error or handle it appropriately.

To fix the problem, we need to ensure that the constructed file paths are contained within a safe root directory. This can be achieved by normalizing the path using path.resolve and then checking that the normalized path starts with the root directory. If the path is not within the root directory, we should reject the operation.

1. Normalize the dir parameter using path.resolve.
2. Check that the normalized path starts with the UPLOAD_BASE_DIR.
3. If the check fails, throw an error or handle it appropriately.

To fix the problem, we need to ensure that the dir parameter is properly sanitized before being used in file system operations. We can achieve this by normalizing the path and ensuring it is contained within a safe root directory. This involves using path.resolve to remove any ".." segments and then checking that the resulting path starts with the root directory.

1. Normalize the dir parameter using path.resolve.
2. Check that the normalized path starts with the UPLOAD_BASE_DIR.
3. If the check fails, throw an error or handle it appropriately.

To fix the problem, we need to ensure that the constructed file paths are validated and contained within a safe root directory. This can be achieved by normalizing the path using path.resolve and then checking that the normalized path starts with the root directory.

1. Normalize the path using path.resolve to remove any ".." segments.
2. Check that the normalized path starts with the root directory.
3. If the path is not valid, handle the error appropriately (e.g., by throwing an exception or returning an error response).

To fix the problem, we need to introduce a validation step to ensure that the timeout value provided by the user is within an acceptable range. This can be done by adding a check in the invoke method of the webpage.controller.ts file to limit the timeout value before it is passed to the emit method of the event-listeners.service.ts file. Additionally, we should update the emit method to handle the validated timeout value appropriately.