Is this a hacking attack? Weird errors in logging

0
Coming from a specific user there are about 70 Errors today in our application log with the following stacktrace. It seems like there is passed a function within a client-server request. Seems to me as a possible attack. What do you think? com.mendix.core.CoreRuntimeException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"type":"ChangeAction","changes":"{Boekhouding.BankTransactieBestand_Bankrekening=5348024557533512\n\t\t\tfor (var i = (start || 0), j = this.length; i < j; i++) {\n\t\t\t\tif (this[i] === obj) { return i; }\n\t\t\t}\n\t\t\treturn -1;\n\t\t};}"}', all database changes executed by this action were rolled back at hG.b(SourceFile:217) Caused by: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"type":"ChangeAction","changes":"{Boekhouding.BankTransactieBestand_Bankrekening=5348024557533512\n\t\t\tfor (var i = (start || 0), j = this.length; i < j; i++) {\n\t\t\t\tif (this[i] === obj) { return i; }\n\t\t\t}\n\t\t\treturn -1;\n\t\t};}"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.c(SourceFile:515) Caused by: java.lang.IllegalArgumentException: Global identifier should be a number (given value: 5348024557533512 for (var i = (start || 0), j = this.length; i < j; i++) { if (this[i] === obj) { return i; } } return -1; };) at ij.<init>(SourceFile:71) at com.mendix.core.objectmanagement.member.MendixObjectReference.getValueFromString(SourceFile:83) at com.mendix.core.objectmanagement.member.MendixObjectReference.getValueFromString(SourceFile:16) at hg.a(SourceFile:68) at hg.a(SourceFile:42) at he.a(SourceFile:34) at he$c.a(SourceFile:56) at he$c.apply(SourceFile:55) at scala.collection.Iterator$class.foreach(Iterator.scala:772) at scala.collection.JavaConversions$JMapWrapperLike$$anon$2.foreach(JavaConversions.scala:781) at scala.collection.IterableLike$class.foreach(IterableLike.scala:73) at scala.collection.JavaConversions$JMapWrapper.foreach(JavaConversions.scala:792) at he.b(SourceFile:55) at he.executeAction(SourceFile:34) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:57) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:457) at hG.b(SourceFile:206) at com.mendix.core.Core.change(SourceFile:728) at gl.execute(SourceFile:65) at jf.a(SourceFile:321) at com.mendix.externalinterface.connector.RequestDispatching$Worker.a(SourceFile:170) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.a(SourceFile:161) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.apply(SourceFile:160) at akka.actor.Actor$class.apply(Actor.scala:545) at com.mendix.externalinterface.connector.RequestDispatching$Worker.apply(SourceFile:156) at akka.actor.LocalActorRef.invoke(ActorRef.scala:910) at akka.dispatch.MessageInvocation.invoke(MessageHandling.scala:25) at akka.dispatch.ExecutableMailbox$class.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:223) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:123) at akka.dispatch.ExecutableMailbox$class.run(ExecutorBasedEventDrivenDispatcher.scala:195) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.run(ExecutorBasedEventDrivenDispatcher.scala:123) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at akka.dispatch.MonitorableThread.run(ThreadPoolBuilder.scala:192)
asked
1 answers
1

Looks like it's passing the identifier and THEN a piece of javascript (which at first sight seems rather harmless). I'm with Michel on this one, looks like a bug in a widget rather than a hacking attempt. But it won't hurt to check it out.

answered