Skip to content
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

Referential integrity plugin - in referint_thread_func does not handle null from ldap_utf8strtok_r #6175

Closed
iamarty3z opened this issue May 15, 2024 · 0 comments · Fixed by #6168
Labels
needs triage The issue will be triaged during scrum

Comments

@iamarty3z
Copy link
Contributor

Issue Description
Referential integrity plugin in the case when processing a line from the logfile. When a null pointer is dereferenced server crash.

Steps to Reproduce
Steps to reproduce the behavior:

  1. enable the plugin using transactions (betxnpostoperation)
  2. set delay > =1
  3. move entry from containerscope
  4. server crash

Expected results
Skipping a line in the log

Additional context
When processing the next line GetNextLine(thisline, MAX_LINE, prfd)
the ldap_utf8strtok_r function may return null.

When passing null to strcasecmp, a crash may occur inside.
The first call ldap_utf8strtok_r(NULL and the ptoken assignment are checked for null, the second and third are not.

There is a solution to this PR:
#6168

@iamarty3z iamarty3z added the needs triage The issue will be triaged during scrum label May 15, 2024
progier389 pushed a commit that referenced this issue May 31, 2024
…oes not handle null from ldap_utf8strtok (#6168)

Added a check for _null_ for the **ptoken** variable when returning from **ldap_utf8strtok_r**.

Issue: #6175

Reviewed by: @progier389
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage The issue will be triaged during scrum
Projects
None yet
1 participant