Closed MaceySoftware closed 3 months ago
I'm able to build and release v7 and 8.
Older than that I'm not sure if I can build it.
Would someone else be able to build it? This is now affecting our pipelines and we are going to have to make them appear as warnings instead of errors which isn't what we really want to do.
If you submit a PR for 5, 6, and 7 I will try to build them.
Or someone I trust can build and provide me with the bin folder so I can build the packages.
Step one is a set of PRs.
Hmm I have never used GIT.. will attempt to hook it up now.
The contributor doc in the repo has instrucciones.
On my phone traveling, so can't provide details.
One that confuses me.
Is this even a security issue for my code base, if I am running 4.8 as it has If Net5_0_OR_GREATER around the code, so this won't even be hit will it? At least in my case.
Happy to make the change still, good learning exercise to get me into GIT and otherwise pipeline will still whine about it and I am sure some third party pen testing application will find it...
It does not affect netfx, no. Only modern dotnet has the feature to dynamically load an assembly.
@rockfordlhotka That is good news. I think we are OK then as all our server stuff is net framework 4.8.
@rockfordlhotka Now we have backfitted everything are we happy for this one to be closed?
Hi All,
Just wondering if this could be backfitted and set out as a small fix to previous versions, as much as I would love to upgrade to CSLA 8.0 I am just not in a position to do this at the moment, but don't want this vulnerability to show up in future testing done by the customer.
https://www.intruder.io/research/path-traversal-and-code-execution-in-csla-net-cve-2024-28698?utm_content=301411509&utm_medium=social&utm_source=twitter&hss_channel=tw-3189900201
Version and Platform CSLA version: 5.3.3 OS: Window Platform: WebAPI