EF1000: Possible SQL injection vulnerability



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I have a dotnet core class library. And after adding Microsoft.EntityFrameworkCore.SqlServer package to project, this Analyzers warning showed up:



EF1000: Possible SQL injection vulnerability.



I have only one single simple entity and a DbContext in project and nothing more. Do you have any idea what is the error about and how to fix it?



I'm using VS 2017 Version 15.8.8, .NET Core 2.1 and EF Core 2.1.4.










share|improve this question






















  • The analyzer will highlight the lines that caused the problem. The analyzer's messages are emitted to the Error and Output window. What is the actual message?

    – Panagiotis Kanavos
    Nov 15 '18 at 12:28












  • It could be a corrupted package as shown in this question

    – Panagiotis Kanavos
    Nov 15 '18 at 12:29

















0















I have a dotnet core class library. And after adding Microsoft.EntityFrameworkCore.SqlServer package to project, this Analyzers warning showed up:



EF1000: Possible SQL injection vulnerability.



I have only one single simple entity and a DbContext in project and nothing more. Do you have any idea what is the error about and how to fix it?



I'm using VS 2017 Version 15.8.8, .NET Core 2.1 and EF Core 2.1.4.










share|improve this question






















  • The analyzer will highlight the lines that caused the problem. The analyzer's messages are emitted to the Error and Output window. What is the actual message?

    – Panagiotis Kanavos
    Nov 15 '18 at 12:28












  • It could be a corrupted package as shown in this question

    – Panagiotis Kanavos
    Nov 15 '18 at 12:29













0












0








0








I have a dotnet core class library. And after adding Microsoft.EntityFrameworkCore.SqlServer package to project, this Analyzers warning showed up:



EF1000: Possible SQL injection vulnerability.



I have only one single simple entity and a DbContext in project and nothing more. Do you have any idea what is the error about and how to fix it?



I'm using VS 2017 Version 15.8.8, .NET Core 2.1 and EF Core 2.1.4.










share|improve this question














I have a dotnet core class library. And after adding Microsoft.EntityFrameworkCore.SqlServer package to project, this Analyzers warning showed up:



EF1000: Possible SQL injection vulnerability.



I have only one single simple entity and a DbContext in project and nothing more. Do you have any idea what is the error about and how to fix it?



I'm using VS 2017 Version 15.8.8, .NET Core 2.1 and EF Core 2.1.4.







.net-core entity-framework-core ef-core-2.1 .net-core-2.1 entity-framework-core-2.1






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 12:22









javad amiryjavad amiry

15.4k847100




15.4k847100












  • The analyzer will highlight the lines that caused the problem. The analyzer's messages are emitted to the Error and Output window. What is the actual message?

    – Panagiotis Kanavos
    Nov 15 '18 at 12:28












  • It could be a corrupted package as shown in this question

    – Panagiotis Kanavos
    Nov 15 '18 at 12:29

















  • The analyzer will highlight the lines that caused the problem. The analyzer's messages are emitted to the Error and Output window. What is the actual message?

    – Panagiotis Kanavos
    Nov 15 '18 at 12:28












  • It could be a corrupted package as shown in this question

    – Panagiotis Kanavos
    Nov 15 '18 at 12:29
















The analyzer will highlight the lines that caused the problem. The analyzer's messages are emitted to the Error and Output window. What is the actual message?

– Panagiotis Kanavos
Nov 15 '18 at 12:28






The analyzer will highlight the lines that caused the problem. The analyzer's messages are emitted to the Error and Output window. What is the actual message?

– Panagiotis Kanavos
Nov 15 '18 at 12:28














It could be a corrupted package as shown in this question

– Panagiotis Kanavos
Nov 15 '18 at 12:29





It could be a corrupted package as shown in this question

– Panagiotis Kanavos
Nov 15 '18 at 12:29












0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53319438%2fef1000-possible-sql-injection-vulnerability%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53319438%2fef1000-possible-sql-injection-vulnerability%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Darth Vader #20

How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

Ondo