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

type error issue (bzar_dce-rpc_consts.zeek) #19

Open
hskte opened this issue Jan 6, 2023 · 4 comments
Open

type error issue (bzar_dce-rpc_consts.zeek) #19

hskte opened this issue Jan 6, 2023 · 4 comments

Comments

@hskte
Copy link

hskte commented Jan 6, 2023

There is type mismatching errors when parsing Sets type arrays.

It should be like : [" "], > " ",

the error messages are here:
error in string and /opt/zeek/share/zeek/site/packages/./bzar/./bzar_dce-rpc_consts.zeek, line 25: type clash (string and drsuapi::DRSReplicaSync) error in /opt/zeek/share/zeek/site/packages/./bzar/./bzar_dce-rpc_consts.zeek, line 25 and string: type mismatch (drsuapi::DRSReplicaSync and string) error in /opt/zeek/share/zeek/site/packages/./bzar/./bzar_dce-rpc_consts.zeek, lines 25-26: inconsistent type in set constructor (set(drsuapi::DRSReplicaSync, drsuapi::DRSGetNCChanges)) error in /opt/zeek/share/zeek/site/packages/./bzar/./bzar_dce-rpc_consts.zeek, lines 25-26: type clash in assignment (BZAR::t1003_006_rpc_strings = set(drsuapi::DRSReplicaSync, drsuapi::DRSGetNCChanges))

@hskte
Copy link
Author

hskte commented Jan 6, 2023

My zeek version is : zeek version 5.1.1

@JustinAzoff
Copy link
Contributor

The reason for this is that the string sets are declared incorrectly:

This:

	const t1003_006_rpc_strings : set[string] =
	{
		# T1003.006 OS Credential Dumping: DCSync
		["drsuapi::DRSReplicaSync"],
		["drsuapi::DRSGetNCChanges"],
	} &redef;

Should be

	const t1003_006_rpc_strings : set[string] =
	{
		# T1003.006 OS Credential Dumping: DCSync
		"drsuapi::DRSReplicaSync",
		"drsuapi::DRSGetNCChanges",
	} &redef;

zeek used to permit this, but it was not correct syntax and it only really worked by accident (and depending on exactly what the mismatch was, might crash)

@JustinAzoff
Copy link
Contributor

ah, and https://github.com/mitre-attack/bzar/pull/16/files already has the fixes for this

@mmguero
Copy link
Contributor

mmguero commented Oct 2, 2023

Should be fixed with #16 being pulled in now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants