핵심 요구사항
- React/Node.js/MongoDB 시큐어 코드 리뷰 및 OWASP Top 10 취약점 식별
- 취약점 직접 패치 및 코드 주석 처리
- 수정 검증을 위한 실제 침투 테스트 수행
- 인증·결제·데이터 저장 등 핵심 영역 보안 강화
- 취약점-패치-재테스트 매핑 보고서 작성
- NDA 체결 및 관련 과거 실적(리다크션 보고서/CVE) 제시
Required stack
필요 기술
ReactNode.jsMongoDBPenetration TestingWeb SecurityOWASPBurp Suite
Project brief
프로젝트 내용
have a production-ready site that was stitched together by several freelancers. While the feature set works, the underlying security clearly does not: I can already spot areas where input is not sanitised and session handling feels weak. I now need a professional who can take the codebase apart, find every vulnerability, patch it, and then prove the fixes hold under pressure.
Here is what I am looking for:
• A full secure-code review of the existing React JS, Node js, and MongoDB line by line where necessary, identifying logic flaws, misconfigurations, and any OWASP Top 10 issues.
• Active penetration testing once the review is complete, so we validate your fixes in a real-world scenario rather than stopping at theoretical findings.
• Clear, developer-ready remediation: update the code yourself, comment the changes, and supply a concise report that maps each vulnerability to its patch and retest results.
The most critical areas—user authentication, payment processing, data storage, and really anything that could be abused—must emerge bullet-proof when you are done. Please show relevant past work (redacted reports or links to resolved CVEs are ideal) so I can see the depth of your experience. If you routinely combine static analysis tools (Burp Suite, OWASP ZAP, SonarQube, etc.) with manual review, mention that as well.
I will grant repository access after NDA. Final acceptance happens only after we rerun penetration tests and everything comes back clean
Here is what I am looking for:
• A full secure-code review of the existing React JS, Node js, and MongoDB line by line where necessary, identifying logic flaws, misconfigurations, and any OWASP Top 10 issues.
• Active penetration testing once the review is complete, so we validate your fixes in a real-world scenario rather than stopping at theoretical findings.
• Clear, developer-ready remediation: update the code yourself, comment the changes, and supply a concise report that maps each vulnerability to its patch and retest results.
The most critical areas—user authentication, payment processing, data storage, and really anything that could be abused—must emerge bullet-proof when you are done. Please show relevant past work (redacted reports or links to resolved CVEs are ideal) so I can see the depth of your experience. If you routinely combine static analysis tools (Burp Suite, OWASP ZAP, SonarQube, etc.) with manual review, mention that as well.
I will grant repository access after NDA. Final acceptance happens only after we rerun penetration tests and everything comes back clean
지원 기회 분석
지원 전에 볼 것
예상 산출물
- 시큐어 코드 리뷰 및 취약점 목록
- 패치가 적용된 코드베이스
- 침투 테스트 결과 및 재테스트 리포트
- 취약점-패치 매핑 보고서
매력 포인트
- 요구 범위와 산출물이 비교적 명확함
확인할 점
- 예산($30~250)이 전체 코드베이스 보안 감사·패치·침투 테스트 범위에 비해 지나치게 낮음
- 입찰 145건으로 경쟁 과열, 클라이언트 이력 정보 없음
- 코드베이스 규모·기간 미명시로 작업량 산정 불가
Client signal
클라이언트 정보
플랫폼에서 상세 정보를 확인하세요.