# How does Application Security detects injection vulnerabilities?

**URL:** <https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300>\
**Category:** Open Q&A\
**Tags:** application-security\
**Created:** [May 30, 2022, 3:49am UTC](https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300 "2022-05-30T03:49:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![frank](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@frank](https://community.dynatrace.com/u/frank)\
**Post date:** [May 30, 2022, 3:49am UTC](https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300/1 "2022-05-30T03:49:20Z")

</div>

Am new to Dynatrace’s Application Security capabilities, so pardon me if my question sounds trivial: the following is an excerpt from&nbsp;[Dynatrace Application Security detects and blocks attacks automatically in real-time](https://www.dynatrace.com/news/blog/automatic-detection-and-blocking-of-attacks/)&nbsp;which hints that Dynatrace performs source/sink tracking or taint propagation to identify injection vulnerabilities.

_With transaction analysis and code-level insights, **Dynatrace detects whenever user-generated inputs are sent to vulnerable application components without sanitization**. With this approach, **you can identify SQL injection attacks** , command injection attacks, and JDNI attacks like log4shell or the H2 vulnerability._

_This means that Dynatrace doesn’t rely on vulnerability databases but is rather able to identify and block such attacks automatically even if they are exploiting unknown weaknesses. A perfect OWASP benchmark score for injection attacks—100% accuracy and zero false positives—impressively proves the precision of our approach._

The examples I’ve come across of Application Security issues Dynatrace is able to identify seem to rely on vulnerability databases such as synk to identify or component vulnerabilities, or am I missing something? I’m not interested in Dynatrace flagging component vulnerabilities without proof-of-exploitability: that is already covered by other SCA tools.

Can someone who’s experienced with Dynatrace Application Security capabilities confirm if it has source/sink tracking and/or taint propagation capabilities that is capable of detecting and preventing injection attacks that are introduced with custom code without code change?

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [May 31, 2022, 11:53am UTC](https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300/2 "2022-05-31T11:53:27Z")

</div>

I believe this is one of the upcoming features in Dynatrace 1.242 / OneAgent 1.241.&nbsp; Details are not publicly available yet - stay tuned.

Until now, the Application Security module relied on the vulnerability list from the vulnerability feed - where SNYK was the (main) source.

---

<div class="post-metadata">

**Author:** ![techean](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/techean/32/227_2.png) [@techean](https://community.dynatrace.com/u/techean)\
**Post date:** [May 31, 2022, 12:19pm UTC](https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300/3 "2022-05-31T12:19:29Z")

</div>

Just a basic info as its not public, we compare the deployed packages with a list of vulnerable packages and the DAVIS act as a security advisor to make the needful action. Code level insights and other data are used to determine the technology packages and code pattern used by any application.

Stay tune

[Application Security Product Tour (dynatrace.com)](https://interact.dynatrace.com/appsec-product-tour/p/1)

---

<div class="post-metadata">

**Author:** ![frank](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@frank](https://community.dynatrace.com/u/frank)\
**Post date:** [June 3, 2022, 1:20am UTC](https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300/4 "2022-06-03T01:20:34Z")

</div>

Thanks both for your replies, that answered my question and more.

Will keep an eye on the upcoming release.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [June 3, 2022, 6:30am UTC](https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300/5 "2022-06-03T06:30:36Z")

</div>

[@frank](https://community.dynatrace.com/user/51691)&nbsp; in the meantime you can check this video from Perform which shows part of it in action (mainly the second half):

> **[Address log4shell with ease - Why integrated runtime security and...](https://www.dynatrace.com/perform-2022-ondemand/breakouts/address-log4shell-with-ease/)**
>
> Securing modern cloud apps in highly dynamic and complex production environments is a big challenge as traditional manual approaches cannot keep up and companies adopt DevSecOps approaches to cover app security end-to-end. Learn how to easily extend...

---

<div class="post-metadata">

**Author:** ![GerhardByrne](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/gerhardbyrne/32/32889_2.png) [@GerhardByrne](https://community.dynatrace.com/u/GerhardByrne)\
**Post date:** [June 7, 2022, 6:24am UTC](https://community.dynatrace.com/t/how-does-application-security-detects-injection-vulnerabilities/35300/6 "2022-06-07T06:24:10Z")

</div>

Hi&nbsp;[@frank](https://community.dynatrace.com/user/51691)&nbsp;,

as already mentioned, the OSS library vulnerability assessment is using our partner Snyk’s best-in-class vulnerability database.

With the upcoming attack protection, we are going a step further and - as you already expected - track user generated input through the code paths to detect injection attacks on custom and library code. This gives us the capability of not only detecting known vulnerabilities, but find undiscovered vulnerabilities in all monitored Java applications.

And that with the flip of a switch - no code changes or configuration necessary.
