-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix: instance creation broken by sanitization guard, silent error swallow, and build failures #2608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -257,8 +257,25 @@ export class WAMonitoringService { | |
| businessId: data.businessId, | ||
| }, | ||
| }); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. suggestion (bug_risk): Consider wrapping instance creation and Setting upsert in a single transaction for atomicity. If the Instance is created but the Setting upsert fails (e.g., transient DB error), you can still end up with an Instance without a Setting, which undermines the intent of this change. Wrapping both operations in Suggested implementation: businessId: data.businessId,
},
});
await this.prismaRepository.$transaction(async (tx) => {
// Ensure Instance creation and Setting record creation happen atomically.
await tx.instance.create({
data: {
businessId: data.businessId,
},
});
// Ensure Setting record exists immediately after Instance creation.
// Prevents FK constraint violations (Setting_instanceId_fkey) in chatbot
// integrations that write to IntegrationSession before setSettings() runs.
await tx.setting.upsert({
where: { instanceId: data.instanceId },
update: {},
create: {
instanceId: data.instanceId,
rejectCall: false,
groupsIgnore: false,
alwaysOnline: false,
readMessages: false,
readStatus: false,
syncFullHistory: false,
},
});
});The |
||
| // Ensure Setting record exists immediately after Instance creation. | ||
| // Prevents FK constraint violations (Setting_instanceId_fkey) in chatbot | ||
| // integrations that write to IntegrationSession before setSettings() runs. | ||
| await this.prismaRepository.setting.upsert({ | ||
| where: { instanceId: data.instanceId }, | ||
| update: {}, | ||
| create: { | ||
| instanceId: data.instanceId, | ||
| rejectCall: false, | ||
| groupsIgnore: false, | ||
| alwaysOnline: false, | ||
| readMessages: false, | ||
| readStatus: false, | ||
| syncFullHistory: false, | ||
| }, | ||
| }); | ||
| } catch (error) { | ||
| this.logger.error(error); | ||
| throw error; | ||
| } | ||
| } | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚨 issue (security): Overriding
instanceNameafter sanitization may reintroduce unsafe data from the raw body.By setting
sanitized.instanceName = body.instanceNameafter callingsanitizeUntrustedInput, you circumvent any validation or filtering that function would apply toinstanceName. IfsanitizeUntrustedInputis responsible for enforcing allowed keys or validating value formats, consider either updating it to explicitly handleinstanceNameor adding explicit validation here before assigning, rather than copying the raw value.